Reader-first guides to AI agent storage, session replay, and coding workflows.
Muse keeps one JSONL per agent under ~/agents — with session_header/item/compaction_checkpoint records, thinking as a first-class citizen, and a source field on every item naming the runtime subsystem that wrote it.
Grok Bot’s sidebar lists every agent, but each durable JSONL lives on the computer that agent is bound to — cloud-box agent-transcripts, not Mac Application Support — with send_message replies and merged group rooms.
Hermes keeps session metadata, token accounting, reasoning, and tool calls in SQLite — with named profiles, Bot Chat, and two different compaction signals.
OpenCode stores sessions, messages, and tool parts in SQLite—not JSONL. Here's the schema, the subagent rows, the compaction trap, and how to read it safely.
Pi stores a session as a JSONL tree, not a flat transcript: entries point to parents, branches can be abandoned, and compaction is its own event.
Cursor SDK agents use a separate sdk-agent-store: SQLite for runs and results, JSONL for prompts. Here's how to join the two safely.
Codex keeps the replay in rollout JSONL, the /resume metadata in SQLite, and renamed threads in an append-only index. Here's how the pieces fit together.
Claude Desktop's Cowork mode writes its audit trail separately from Claude Code. Here's how Dispatch sessions are stored and replayed.
vibe-replay tracks AI coding activity across machines and tools. Explore GitHub-style heatmaps, streaks, model usage, and privacy-aware shareable profiles.
We captured Claude Code's /simplify workflow as an interactive replay to see file discovery, parallel agents, fixes, and verification—not just the final diff.
A source-map discovery clarified Claude Code's JSONL fields, compaction markers, MCP names, and pricing metadata. Here's what changed in replay tooling.
Find Cursor chat history on disk: state.vscdb, agent-transcripts, ~/.cursor/chats, and globalStorage — paths, how to recover sessions, and what each layer stores.
Claude Code stores session history, tool calls, file snapshots, and usage data under ~/.claude/. Here's where the files live and how to inspect them safely.
An interactive replay makes AI coding sessions searchable: prompts, tool calls, abandoned paths, and the final result in one self-contained view.