Faithful replay
Thinking chains, tool calls paired with their results, structured diffs and pasted screenshots render the way they happened on screen.
How sessions are replayed
Claude Code, Codex, Grok Build, Kimi Code, Pi, Antigravity CLI and opencode each store their session history in a different place and a different format. Sessions Viewer reads all of them into the same project, session and conversation view.
Sessions Viewer reads the files each CLI already writes, in place. The reference pages document every layout, with jq and sqlite3 commands for reading a transcript without the app.
| Agent | Default location | Format |
|---|---|---|
| Claude Code | ~/.claude/projects/ | One JSONL file per session |
| Codex | ~/.codex/sessions/ | One JSONL file per session, bucketed by date |
| Grok Build | ~/.grok/sessions/ | One directory per session |
| Kimi Code | ~/.kimi-code/sessions/ | One directory per session |
| Pi | ~/.pi/agent/sessions/ | One JSONL file per session |
| Antigravity CLI | ~/.gemini/antigravity-cli/brain/ | One directory per conversation |
| opencode | ~/.local/share/opencode/opencode.db | A single SQLite database |
The app is free and open source under the MIT license, and runs on macOS, Windows and Linux. Download the latest release or start with the guide.