AgentsView Session Archive
Search coding-agent sessions locally and inspect token use, estimated costs, and activity.
- Source repo
- kenn-io/agentsview
- Stars
- ★ 6.5k
- Last updated
- today
- License
- MIT
- Primary language
- Go
- FA score
- 76/100 · Good
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex · Claude Code
- Cost
- Free, no paid service needed
- Setup effort
- Low · running in minutes
- You'll need
- Typical use
- A developer using Claude Code, Codex, and other tools wants one local interface to search and revisit sessions.
- Not a fit if
- Developers who need session browsing inside their IDE
- Teams that need Cursor attribution stats synced to PostgreSQL
- Website
- agentsview.io ↗ set on GitHub
- Maintenance
- Commits in the last 30 dayslast commit 2026-11-21latest release v0.47.0 (2026-11-09)+7.9 ★/day over 7 days
- Source review
- 76/100 · Good
What does this agent do, and when should you use it?
AgentsView is a local-first session browser and analytics tool for coding agents, with a Go CLI, a Go-served web UI, and desktop apps for macOS and Windows. On first run it discovers sessions from supported agent directories, syncs them into a local SQLite archive, and serves the UI at 127.0.0.1:8080 by default. The CLI lists and searches sessions, reports token use and estimated costs, and emits windowed statistics; the UI provides full-text search, session viewing, cost dashboards, and activity analytics. Optional PostgreSQL, ClickHouse, and DuckDB targets can receive pushed or mirrored archive data and serve it read-only. Session content stays local by default; telemetry can be disabled, while semantic search, GitHub Gist export, and remote sync involve their configured external services.
AgentsView reads local session files from Claude Code, Codex, and other supported tools, parses them, and stores sessions and messages in SQLite. agentsview serve starts the server, web UI, sync, and file watchers; agentsview daemon start runs it in the background. Commands such as agentsview session list, agentsview usage daily, and agentsview stats read the archive and return sessions, cost summaries, and analytics. agentsview session search supports full-text search, with semantic or hybrid search available after configuring an embeddings endpoint. The web UI displays transcripts, token use, costs, activity heatmaps, and tool usage; the REST API exposes per-session usage at /api/v1/sessions/{id}/usage. Optional pg push, clickhouse push, and duckdb push copy the SQLite archive to those destinations for read-only serving or analysis.
- A developer using Claude Code, Codex, and other tools wants one local interface to search and revisit sessions.
- An individual developer wants daily or per-model token and estimated-cost reports across coding agents.
- A team wants to push local archives to PostgreSQL for a shared, read-only dashboard.
- An analyst wants a DuckDB mirror or a ClickHouse copy for read-only querying.
- A user building automation wants CLI JSON output, stats, or the per-session REST API for scripts.
Key setup facts
Pulled from the install and usage notes below. The project README has the current values.
- Install / run
curl -fsSL https://agentsview.io/install.sh | bashbrew install --cask agentsviewdocker run --rm -p 127.0.0.1:8080:8080 \
- Ports
8080- Environment variables
CLAUDE_PROJECTS_DIR- Install notes cover
- Windows · macOS · Linux · Docker
How do you install or deploy this agent?
Install the CLI on macOS or Linux with:
curl -fsSL https://agentsview.io/install.sh | bashOn Windows, use PowerShell:
powershell -ExecutionPolicy ByPass -c "irm https://agentsview.io/install.ps1 | iex"The desktop app is available for macOS and Windows; on macOS, Homebrew is also supported:
brew install --cask agentsviewThe Docker image is another documented option. Mount agent session directories and set their matching environment variables so the container can discover those sessions:
docker run --rm -p 127.0.0.1:8080:8080 \
-v agentsview-data:/data \
-v "$HOME/.claude/projects:/agents/claude:ro" \
-e CLAUDE_PROJECTS_DIR=/agents/claude \
ghcr.io/kenn-io/agentsview:latestHow do you use this agent?
On first run, AgentsView discovers supported session sources, syncs them into SQLite, and starts the local web UI:
agentsview serveOpen http://127.0.0.1:8080 in a browser. Common CLI commands include:
agentsview daemon start
agentsview session list
agentsview usage daily
agentsview stats --format jsonSearch with agentsview session search; semantic search requires an OpenAI-compatible embeddings endpoint. Per-session usage is available from the CLI or REST API:
agentsview session usage <id>
curl http://127.0.0.1:8080/api/v1/sessions/<id>/usageDaily usage reports read the saved archive. Run agentsview sync first to include new changes from source directories.
What are this agent's strengths and limitations?
- Consolidates local sessions from more than 20 coding agents in SQLite, with FTS5 full-text search and project/date filters.
- Provides cross-agent usage, cost, and analytics through CLI reports, JSON output, and a per-session REST API.
- Keeps SQLite as the primary archive while offering PostgreSQL, ClickHouse, and DuckDB as optional push or read-only mirror backends.
- Offers CLI, web UI, macOS and Windows desktop apps, and Docker deployment.
- Each agent needs an accessible local session directory; Docker deployments must mount directories and set matching environment variables.
- Semantic search requires an OpenAI-compatible embeddings endpoint; cost estimates depend on available pricing, and some proprietary models may be unpriced.
- PostgreSQL, ClickHouse, and DuckDB features require extra backend configuration; remote access also requires appropriate authentication, TLS, or a trusted proxy.
- The README does not specify desktop OS version requirements; source development requires Go 1.27+ (CGO) and Node.js 24.11+.
How does this agent compare with similar options?
The README presents SQLite as the primary archive and PostgreSQL, ClickHouse, and DuckDB as optional shared or mirror backends. SQLite supports writes and FTS5 indexed search; remote backends serve read-only. DuckDB search uses substring or regex fallback, while SQLite FTS5 is the indexed search path.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| AgentsView Session Archive This agent | 76 · Good | CLIFree | ★ 6.5k | today | Go | Codex · Claude Code |
| LeanCTX Context Intelligence | 69 · Some gaps | CLIFree + model costs | ★ 4k | 5d ago | Rust | Codex · Claude Code · OpenAI API · Claude API |
| ccxray | 76 · Good | CLIFree + model costs | ★ 296 | 4d ago | JavaScript | Claude Code · Claude API |
| Agent Deck | 74 · Some gaps | CLIFree + model costs | ★ 1.3k | 6d ago | Go | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows loopback binding by default, read-only session mounts in container examples, authentication guidance for remote access, and selectable full, transcripts, or usage archive policies with clear limits and rebuild consequences. Deductions: the default full policy retains sensitive conversation content, and installation examples pipe downloaded scripts into shells; optional semantic search, cloud sync, and export have user-configured external effects, but the supplied files do not fully describe confirmation steps or each data flow.
The README, Quick Start, and configuration guide are broadly consistent about daemon behavior, archive policies, deployment, and limitations; they describe behaviors such as preserving the active log if rotation fails and SHA-256 verification by the installer. Deducted because network services and optional components are involved without a complete account of failure behavior for each dependency; source excerpts cannot establish runtime correctness.
The product covers CLI, desktop, containers, CI, forwarded access, multiple platforms, and many session sources. It states that Aider is opt-in, Amp support is deprecated, Codex Cloud is disabled by default, and containers see only mounted sources. Deducted because the supplied skills mainly describe maintenance-task triggers, so they do not establish equally precise end-user capability triggers throughout the product.
Documentation is organized around installation, operation, configuration, data policy, and deployment, with detailed commands, platform differences, examples, and limitations; license metadata says MIT. Deducted because the license text and changelog contents are not supplied, only the latest version and a changelog link. Publisher identity is unknown, and repository maintenance instructions do not clearly identify who owns product maintenance or long-term support.
The product offers local cross-agent session search, cost reporting, analytics, and multiple output paths; CLI commands, JSON output, a REST API, and screenshots support interactive and scripted use. Deducted because full archiving and some advanced features can add storage or configuration costs, and the supplied material does not quantify resource use enough to assess cost-benefit fully.
Feature claims are supported across the README, Quick Start, configuration guide, and main entry point; the materials distinguish defaults, optional settings, and stated limitations. Deducted because many implementation details are documented claims that the supplied source excerpts do not independently corroborate, and there is no execution or independent test evidence.
- The default full archive retains parsed messages, reasoning text, tool metadata, and results. Environments containing sensitive data should choose a narrower policy first; policy changes require restart and rebuild, and discarded content cannot be recovered from the archive.
- Container and non-loopback access require deliberate session-directory mounts and authentication. Optional features such as semantic search, cloud sync, and Gist publishing may involve external services; review their specific configuration before enabling them.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
New features - Review daily problems in the Friction Log, including corrections, tool errors, and recurring patterns linked to exact messages. Browse dates, download Markdown, or read findings through the CLI and MCP. Enable it with [friction] enabled = true. - Turn Friction Log patterns into Kata issues, link existing issues, or remove links from the page or CLI. Enable hourly automatic filing with [friction.kata] auto_file = true. …View on GitHub ↗ -
Release notes excerpt
Improvements - Antigravity CLI sessions show plaintext transcripts with model and token usage attached to the matching model replies. Bug fixes - Antigravity sessions parse again on read-only mounts, including read-only Docker volumes. - Archived Antigravity CLI replies stay intact when the session database cannot be read. - Repeated prompts remain separate turns in Antigravity CLI sessions. Existing archives are reprocessed to recover missing turns. - Docker builds no longer fail because a required Claude.ai Chrome extension file is missing.View on GitHub ↗ -
Release notes excerpt
New features - Sync Claude.ai chats through Chrome, including Google sign-in. Run agentsview chrome setup, load the printed extension folder at chrome://extensions, and restart AgentsView before using Import > Claude.ai. - Import ChatGPT dot, Codex web, and Codex cloud task chats as searchable sessions with the opt-in codex-cloud source. Chats without token counts show OpenAI's plan usage figures. Configure this source on one machine only. …View on GitHub ↗
FAQ
Do I need a paid model or API key to use AgentsView?
Does session content get uploaded to the cloud?
AGENTSVIEW_TELEMETRY_ENABLED=0 or TELEMETRY_ENABLED=0; shared backends, semantic-search endpoints, and Gist export are optional external paths.Why is an agent or session missing from the UI?
AIDER_DIR or agents.aider.dirs; Docker also needs the source directory mounted.Will cost figures exactly match billing?
Can I open the local server through a remote browser?
--public-url or trusted origins for forwarding or proxy access. If exposing the UI beyond loopback, enable --require-auth; these settings do not create an external listener or proxy.Is AgentsView Session Archive open source?
Is AgentsView Session Archive safe to use?
Is AgentsView Session Archive still maintained?
Who makes AgentsView Session Archive?
What is AgentsView Session Archive's official website?
Thanks — we use this to improve the page.