PostgreSQL
Push to a shared backend.
An installable auto-push service mirrors each machine's archive into PostgreSQL; a read-only server presents the merged fleet. PostgreSQL sync.
AgentsView brings your AI coding sessions into one searchable archive. Browse recorded conversations from more than 60 agent formats, compare activity and costs, and reuse lessons from past work. The archive stays on your machine unless you turn on a feature that shares it.
curl -fsSL https://agentsview.io/install.sh | bash
macOS and Linux · Windows, desktop app, pip, and Docker installs
01 / Record
A background server watches the session directories your agents already write and imports supported formats into a local SQLite archive. It finds the default directories automatically. You can configure other locations. Start a session in one window and watch it stream into AgentsView in another.
02 / Observe
The Activity dashboard shows peak concurrency and the exact moment it happened, active versus idle time, agent-minutes across parallel sessions, and cost. Scope it to any day, week, month, or custom range, and filter by project, agent, and machine. Live sync streams new messages into the UI as sessions run.
03 / Account
Token and cost reports read from the pre-indexed archive instead of reparsing raw session files every time. Pricing tracks LiteLLM and OpenRouter rates with an offline fallback, and cache-aware accounting covers prompt-cache creation and reads.
04 / Understand
Find a conversation by project and date in the command palette, or open it by ID with Ctrl/Cmd+G. Full-text search matches words; opt-in semantic and hybrid search match by meaning. Health scores and quality signals link back to the transcript so you can check the evidence.
05 / Remember
Recall (experimental) extracts decisions, warnings, and project facts from your archive. Each entry links to the messages that support it. Generated Insights write model-authored reports over an explicit session scope and manage them alongside the corpus.
06 / Feed back
The same archive is available to your agents through a CLI, a REST API, and an MCP server. An agent can check what a previous session already tried, quote its own history, or watch its spend mid-run.
07 / Share
SQLite is the local archive of record. From there, push parsed sessions to PostgreSQL or ClickHouse, mirror into DuckDB, read provider files from S3, or keep original source files in hosted storage.
DuckDB / ClickHouse
Mirror into DuckDB for local or Quack reads, or push to ClickHouse and serve the dashboard there. Keep session edits in SQLite.
Filesystem
Point a primary viewer at out-of-band copies of native session directories, including S3-backed sources. Filesystem sync. Hosted raw sync
Upload original session files to an operator-managed server with device credentials and resumable transfers. Hosted browsing still requires PostgreSQL sync. Hosted raw sync.
Remote access
Loopback by default, with explicit flags for SSH forwards, remote dev environments, and authenticated non-loopback exposure. Remote access.
Artifact folders
Move immutable session revisions between trusted folders for experimental portable workflows. Artifact folder sync.
08 / Own
Your agent transcripts can contain source code, credentials, paths, and private conversations. AgentsView starts with one local SQLite archive and a loopback-only server. Session content leaves the machine only through features you choose.
Default
Browse, search, report, and run local Recall workflows without sending session content to an AgentsView account.
Your choice
Configure PostgreSQL, ClickHouse, remote DuckDB, Generated Insights, GitHub publishing, or hosted raw sync only when that outcome is worth sending data.
Visible boundaries
Each sharing feature documents what it sends, where it goes, and which controls apply. Privacy details.
09 / Start
Install AgentsView and it finds the sessions that are already on your machine. The guide walks the whole loop in five minutes; the docs cover installation, workflows, and exact command behavior.