claude-devtools — Your Claude is coding blind

# claude-devtools > claude-devtools is a free, open-source debugging tool for Claude Code. It reads the session logs already saved to `~/.claude/` on your machine and reconstructs everything Claude Code's terminal hides — exact file paths, tool call inputs and outputs, extended thinking, per-turn token attribution, subagent execution trees, and compaction events — in a structured, searchable interface. It does not wrap, modify, or proxy Claude Code; it is a read-only viewer for the JSONL transcripts Claude Code already writes to disk. Since Claude Code v2.1.20, the terminal collapsed detailed output into opaque summaries (`Read 3 files`, `Edited 2 files`) with no file paths, no diffs, and no thinking content. The only built-in alternative is `--verbose`, which dumps raw JSON including internal system prompts. claude-devtools is the middle ground: structured access to the same data Claude Code already records, with zero configuration, no API keys, and no network calls. Distribution: Electron app for macOS (Apple Silicon + Intel), Windows, Linux, plus a standalone Docker / Node.js server (`docker compose up`, port 3456). MIT license. Project repo: https://github.com/matt1398/claude-devtools. ## Documentation - [Docs hub](https://claude-dev.tools/docs): Index of all guides and reference pages. - [What is claude-devtools?](https://claude-dev.tools/docs/what-is): Overview, distribution, and what the tool does and doesn't do. - [How to debug a Claude Code session](https://claude-dev.tools/docs/debugging): Practical entry point — what claude-devtools exposes that the terminal hides. - [Install claude-devtools](https://claude-dev.tools/docs/installation): Homebrew, direct download, Docker. - [Reading Claude Code session transcripts](https://claude-dev.tools/docs/transcripts): Chronological view, per-tool renderers, cross-session search, export. - [How to debug Claude Code tool calls](https://claude-dev.tools/docs/tool-calls): Specialized viewers for Read, Edit, B