![\"claude-devtools\"](\"resources/icons/png/1024x1024.png\"){kind=icon}
\n\n \n
\n Terminal tells you nothing. This shows you everything.\n
\n A desktop app that reconstructs exactly what Claude Code did — every file path, every tool call, every token — from the raw session logs already on your machine.\n
\n ![\"Website\"](\"https://img.shields.io/badge/Website-claude--dev.tools-blue?style=flat-square\"){kind=icon}
![\"Latest](\"https://img.shields.io/github/v/release/matt1398/claude-devtools?style=flat-square&label=version&color=blue\")
![\"CI](\"https://github.com/matt1398/claude-devtools/actions/workflows/ci.yml/badge.svg\"){kind=icon}
\n ![\"Downloads\"](\"https://img.shields.io/github/downloads/matt1398/claude-devtools/total?style=flat-square&color=green\")
![\"Platform\"](\"https://img.shields.io/badge/platform-macOS%20%7C%20Windows-lightgrey?style=flat-square\"){kind=icon}
\n No API keys. No configuration. Just download, open, and see everything Claude Code did.\n
\n\n\n \n
\n\n---\n\n## Installation\n\n### Download Binary\n\n| Platform | Download | Notes |\n|----------|----------|-------|\n| **macOS** (Apple Silicon) | [`.dmg`](https://github.com/matt1398/claude-devtools/releases/latest) | Drag to Applications. On first launch: right-click → Open |\n| **Windows** | [`.exe`](https://github.com/matt1398/claude-devtools/releases/latest) | Standard installer. May trigger SmartScreen — click \"More info\" → \"Run anyway\" |\n\nThe app reads session logs from `~/.claude/` — the data is already on your machine. No setup, no API keys, no login.\n\n### Install via npm\n\n```bash\n# Install globally\nnpm install -g claude-devtools\n\n# Or run directly with npx\nnpx claude-devtools\n```\n\nThe installer automatically downloads the platform-specific binary for your OS (macOS, Windows, or Linux).\n\n---\n\n## Why This Exists\n\n### Claude Code stopped telling you what it's doing.\n\nRecent Claude Code updates replaced detailed tool output with opaque summaries. `Read 3 files`. `Searched for 1 pattern`. `Edited 2 files`. No paths, no content, no line numbers. The context usage indicator became a three-segment progress bar with no breakdown. To get the details back, the only option is `--verbose` — which dumps raw JSON, internal system prompts, and thousands of lines of noise into your terminal.\n\n**There is no middle ground in the CLI.** You either see too little or too much.\n\nclaude-devtools restores the information that was taken away — structured, searchable, and without a single modification to Claude Code itself. It reads the raw session logs from `~/.claude/` and reconstructs the full execution trace: every file path that was read, every regex that was searched, every diff that was applied, every token that was consumed — organized into a visual interface you can actually reason about.\n\n### The wrapper problem.\n\nThere are many GUI wrappers for Claude Code — Conductor, Craft Agents, Vibe Kanban, 1Code, ccswitch, and others. I tried them all. None of them solved the actual problem:\n\n**They wrap Claude Code.** They inject their own prompts, add their own abstractions, and change how Claude behaves. If you love the terminal — and I do — you don't want that. You want Claude Code exactly as it is.\n\n**They only show their own sessions.** Run something in the terminal? It doesn't exist in their UI. You can only see what was executed through *their* tool. The terminal and the GUI are two separate worlds.\n\n**You can't debug what went wrong.** A session failed — but why? The context filled up too fast — but what consumed it? A subagent spawned 5 child agents — but what did they do? Even in the terminal, scrolling back through a long session to reconstruct what happened is nearly impossible.\n\n**You can't monitor what matters.** Want to know when Claude reads `.env`? When a single tool call exceeds 4K tokens of context? When a teammate sends a shutdown request? You'd have to wire up hooks manually, every time, for every project.\n\n**claude-devtools takes a different approach.** It doesn't wrap or modify Claude Code at all. It reads the session logs that already exist on your machine (`~/.claude/`) and turns them into a rich, interactive interface — regardless of whether the session ran in the terminal, in an IDE, or through another tool.\n\n> Zero configuration. No API keys. Works with every session you've ever run.\n\n---\n\n## Key Features\n\n### :mag: Visible Context Reconstruction\n\n![\"Website\"](\"https://img.shields.io/badge/Website-claude--dev.tools-171717?logo=googlechrome&logoColor=white&style=flat\"){kind=icon}
\n ![\"Download](\"https://img.shields.io/badge/macOS-Download-black?logo=apple&logoColor=white&style=flat\"){kind=icon}
\n ![\"Download](\"https://img.shields.io/badge/Windows-Download-0078D4?logo=windows&logoColor=white&style=flat\"){kind=icon}
\n