macOS · Open Source · Local-first
Codex, Claude, Cursor and ten more write sessions to your Mac all day. Agent Sessions reads every one of them — full-text search, transcripts with tool calls and images, and a resume command that puts you back in the CLI you left.
Codex and Claude also get a burn meter: live per-session rate against your 5-hour and weekly limits, priced per model.
brew install --cask jazzyalex/agent-sessions/agent-sessions
Desktop apps and CLI tools side by side, each labelled with the surface it came from. New in 5.0: agents are plug-in adapters, Qwen Code joins as the thirteenth source, and adding the agent you use is a documented recipe.
| Agent | Surfaces | Resume | Quota Meter |
|---|---|---|---|
| Codex | Desktop · CLI · VS Code | Yes | 5h · weekly · $/h |
| Claude | Desktop · CLI | Yes | 5h · weekly · $/h |
| Cursor | IDE · CLI | Yes | — |
| Antigravity | CLI | Yes | — |
| GitHub Copilot | CLI | Yes | — |
| OpenCode | CLI | Yes | — |
| Pi | CLI | Yes | — |
| Hermes | CLI | Yes | — |
| Kimi Code | CLI | Yes | — |
| Grok CLI | CLI | Yes | — |
| Qwen Codenew in 5.0 | CLI | Yes | — |
| OpenClaw | CLI | — | — |
| Add your agent → | Twelve files, each with a test |
The Quota Meter reads Codex and Claude usage windows — the other agents don't publish a quota to meter. Every agent above is searchable, browsable and counted in Analytics.
Apple Notes-style search across all agents and within a single session. Inline image support and an Image Browser for visual output from Codex, Claude, and OpenCode.
Right-click a supported CLI session to copy the exact resume command, or open it directly in Terminal.app, iTerm2, or Warp.
Manage archived sessions — delete, reveal, and diagnose with archive status tooltips.
Flip cards with sparklines: session trends, agent breakdowns, time-of-day heatmaps.
How fast each session burns your plan — and how much you have left before you run out. Quota Meter reads your Codex and Claude 5-hour and weekly limits as a live burn rate against your own plan, so one glance tells you which sessions eat your quota and how long until reset. Three ways to keep it in view:
$ lens rates each model in a session separately, so an Opus orchestrator driving Sonnet subagents is costed at what each actually runs at rather than blended into one number.
Sessions search with transcript and image preview
Saved Sessions with restore actions
Image Browser for visual session outputs
Menu bar status strip
Analytics dashboard filtered to one project
Where each agent keeps its sessions, what Agent Sessions reads, and where the boundaries are.
How CLI, Desktop, and VS Code rollout history is read from ~/.codex/sessions.
Where OpenCode stores session data and how to browse old runs locally.
What Claude Code writes to local transcripts and where the boundary is.
How Cursor Agent transcripts are read from Cursor's local storage.
How Hermes sessions in ~/.hermes/state.db become searchable history.
How OpenClaw JSONL sessions are discovered, searched, and kept separate.