Search across agent sessions
AgentsView imports session histories from Codex, Claude Code, Cursor, and more than 20 other coding agents into a local SQLite database. Its web interface and CLI can search messages, tool calls, and tool results, while its usage reports combine token and estimated cost data across agents.
This is useful when the answer already exists in an old session but you cannot remember which agent did the work. Search for a feature name, rejected tool, or error message and read the surrounding exchange before starting the work again.
We tested v0.40.1 against Swipe’s live Codex history. After limiting the import to the Swipe repository, it indexed the main issue thread and six research threads. Searches recovered every place several rejected issue candidates had appeared, including the tool inputs and results that explained why they were rejected.
Scope the first import
On first run, AgentsView discovers supported session directories automatically.
That convenience can pull in much more than the current project. In our first
test it also found unrelated sessions until we set an exact
sync_include_cwd_prefixes scope.
Start with one project whose history you understand. Check the imported session
list before searching it, especially on a machine used for client or personal
work. The data directory defaults to ~/.agentsview/, and the server binds to
localhost unless you configure remote access.
AgentsView is local-first, not necessarily offline in every configuration. Its optional model-backed insights, semantic search providers, GitHub Gist sharing, Postgres, DuckDB, S3 session roots, and remote-host sync can send or copy data elsewhere. It also performs an update check and anonymous liveness request unless disabled. Leave those features off when local SQLite search is enough.
Install and limitations
AgentsView ships as a CLI, desktop app, Docker image, and release binaries. The project is MIT licensed and moving quickly; v0.40.1 was the current release when we checked it.
Session formats belong to the agent vendors and can change without notice. A successful import proves that AgentsView parsed the available history, not that every tool call or cost field was recorded by the original agent. Project scope also needs deliberate configuration: pointing one environment variable at a directory does not by itself exclude every other auto-discovered source.