Local History Guide / Claude Code
Claude Code JSONL History: Search Local Claude Code Sessions on macOS
Claude Code transcripts often become the only durable record of an implementation: prompts, assistant responses, tool calls, command output, file paths, and errors. Agent Sessions indexes those local JSONL transcripts so old Claude Code work is searchable beside the other coding agents on your Mac.
Agent Sessions reads local transcript files in read-only mode. It does not upload Claude transcripts or claim access to hidden model/runtime state.
Where Claude Code Stores Local Data
Standard Claude Code session history lives under:
~/.claude/projects/<encoded-cwd>/<session-id>.jsonlAgent Sessions also scans configured Claude roots, CLAUDE_CONFIG_DIR, CLAUDE_CONFIG_DIRS, and Claude Desktop local-agent-mode roots when they are present.
What Agent Sessions Does
- Lists Claude Code sessions by project, time, and source surface.
- Full-text searches prompts, assistant text, command output, tool calls, tool results, file paths, and error text.
- Shows readable transcript timelines instead of raw JSONL.
- Keeps Claude rows separate from Codex, OpenCode, Cursor Agent, Hermes, OpenClaw, Gemini, Copilot, and Pi.
- Supports resume workflows where the installed Claude command exposes a compatible resume mode.
Recovery Boundary
The important boundary is transcript context versus hidden runtime state. Agent Sessions can search and display content Claude wrote to disk. It cannot recover model internals, encrypted state, remote-only context, or information that was never persisted locally.