kenn-io / agentsview

---
last_edited: 2026-10-09
---
# agentsview
Browse, search, and track costs across your AI coding agents. Your session
archive stays on your machine unless you choose a feature that shares it.
This README and the documentation follow `main`.
The latest release is **v0.45.0**. Check the
changelog for what it includes.
Version 0.45.0 adds Spanish, Junie/OMO/StepCode sessions, message-frequency
charts, and conversation-memory plugins for Claude Code and Codex. Review tool
errors and recovery in the transcript, approve extracted Recall entries, and
compare prompt volume including cache reads and writes.
## Install
**macOS and Linux:**
 [code] 
**Windows (PowerShell):**
 [code] 
Or download the **desktop app** (macOS / Windows) from
GitHub Releases or via
homebrew: `brew install --cask agentsview`
On macOS, see
Use the bundled CLI
for terminal setup and the required first launch. For Macs managed over SSH, use
the standalone CLI installer above.
Or run the published Docker image:
 [code] 
## Quick Start
 [code] 
On first run, agentsview discovers sessions from every supported agent on your
machine, syncs them into a local SQLite database, and serves a web UI at
`http://127.0.0.1:8080`.
The daemon is the server: the web UI, API, session sync, and file watchers share
one process. Choose `serve` for a foreground process or `daemon start` for a
background process. Running `serve` when a compatible daemon is already running
reports its URL and exits. `daemon stop` and `serve stop` both stop that
writable server, including sync; `serve stop` also stops read-only mirror
servers for the same data directory.
For custom directories, additional agent homes, and supported S3 sources, see
Session discovery.
The same guide explains how to choose
what content to archive.
The desktop app and ordinary session CLI commands share a detached local daemon
and start one when needed. Dedicated diagnostics such as
`db adopt-machine --list` and `doctor sync` read the archive without starting
it. Commands such as `sync`, `usage`, `token-use`, `pg push`, `duckdb push`, and
`clickhouse push` auto-start the daemon when needed. Daily usage reports read
saved archive data; run `agentsview sync` first to include new source changes.
The server remains running after these commands exit and also serves the web UI.
For a one-shot sync with no background server, stop the daemon first and run
`AGENTSVIEW_NO_DAEMON=1 agentsview sync`.
Use `agentsview daemon start` when you want to start the writable SQLite daemon
explicitly. It loads the normal effective configuration from `config.toml` and
supported environment variables; `daemon start` and `daemon restart` accept no
serve-specific flags. Background daemons self-exit after an idle period unless a
client request or daemon-owned job is active.
The existing `agentsview serve --background`, `agentsview serve status`, and
`agentsview serve stop` commands remain available. Use `serve --background` when
a one-off daemon needs a serve-only flag,