claude-code-trace

Claude Code Trace

Claude Code Trace is a viewer for the session logs Claude Code keeps on your machine
(~/.claude/projects/*.jsonl). It turns raw JSONL into a readable conversation, follows live
sessions as they run, and can score how efficiently an agent worked. It runs as a desktop app,
a web app, or a terminal UI, and nothing leaves your machine unless you ask for an analysis.

Features

- Log viewer — every session as a conversation, with expandable tool calls, thinking,
  tool results, sub-agents, token counts and timestamps. Edit tool calls show as word-level diffs.
- Live tailing — an open session updates as Claude Code writes to it, and the picker shows
  which sessions are still running.
- Session picker — sessions grouped by date and project, searchable by what you asked.
- MCP tool calls — mcp calls get readable names, e.g. MCP figma.
- Debug log and team views — Claude Code's debug log and team task boards, when a session has them.
- Efficiency analysis (optional) — sends a redacted summary of a session to
  Jev and shows trace-linked findings: repeated work, thrashing, recovery,
  token use. You see the exact payload and confirm before anything is sent.
- Source plugins — Claude Code is built in; other session sources can be switched on in
  Settings. See Plugins.
- Three front ends — desktop (Tauri), web, and terminal UI (Textual), all reading from the
  same backend.

Plugins

Each session source is a plugin with its own folder on every part of the app. The picker, views
and settings show whatever the enabled plugins provide.

Turn optional plugins on under Settings → General → Sources. With more than one on, the
picker gets an All / per-source filter. Antigravity conversations are read-only, and you can point
it at a different brain directory in…