Claude DevTools

Claude DevTools (also styled claude-devtools) is an open-source desktop inspector for Claude Code sessions. It does not wrap or replace Claude Code. Instead it reads the session logs already stored under ~/.claude/ on your machine and reconstructs what the agent actually did: thinking steps, tool calls, diffs, subagent trees, token attribution, and project memory files. Why it exists: as Claude Code matured, terminal UI sometimes collapsed rich traces into opaque summaries. Community backlash against "coding blind" experiences led to tools that restore visibility without forcing --verbose JSON spam. As of August 2026 the project markets itself to 50,000+ developers, ships macOS (Apple Silicon and Intel), Windows, and Linux builds, and installs on Mac via brew install --cask claude-devtools. It is MIT licensed, requires no API keys, and makes zero outbound calls for core inspection. That privacy posture suits developers who dislike SaaS log uploads. Pricing is free. There is no premium tier. You already pay Anthropic for Claude Code usage; DevTools only visualises local artifacts. Relationship to other tools: complementary to Vibe Notch / Claude Island (live status) rather than competing. DevTools is forensic and analytical after or during sessions; notch apps are real-time HUDs. It is not an official Anthropic product, though it is tightly coupled to Claude Code log formats and must track upstream changes. On Mac, the app is a practical companion for anyone on Pro/Max who wants to understand token burn, debug why an agent went sideways, or compare two prompt strategies side by side. If you only run Claude Code once a month, you may not need it. If Claude Code is daily infrastructure, DevTools quickly pays for itself in saved confusion, at $0 software cost. For teams, Claude DevTools becomes a coaching instrument: leads can open a junior's session (with consent and local access) and show exactly where the agent reread the same failing test fifty times. That teaching moment is hard to recreate from a final git diff alone. In consulting settings, DevTools also helps justify invoices. You can show that a day of agent work touched the right services rather than thrashing unrelated packages. Technical caveats worth repeating: because the tool depends on on-disk log schemas, a Claude Code upgrade can temporarily break parsing until DevTools ships a matching release. Keep both tools reasonably current. If you encrypt home directories or use unusual Claude config locations, point the app at the correct paths. On managed Macs, ensure endpoint security tools do not quarantine the app when it reads many small session files quickly. Feature depth in practice: context reconstruction charts often reveal that half of a '200k context' feeling is tool output residue and repeated file reads, not your carefully written prompts. Cleaning CLAUDE.md and adding ignore patterns can cut costs more than switching from Opus to Sonnet. Subagent trees similarly show whether parallelisation helped or merely multiplied confusion. Notification triggers on.env access are the closest thing to a runtime seatbelt DevTools offers, configure them before the first untrusted repo experiment. Comparison with simply using jq on JSONL logs: scripts are fine for one-off forensics, but DevTools wins for daily navigation, multi-pane compare, memory browsing, and SSH remote hosts. Comparison with IDE local history: IDEs show code evolution, not why the agent chose a tool sequence. You want both. Comparison with Anthropic's official UIs: official products optimise for doing work; DevTools optimises for understanding work already done. In short, if Claude Code is part of your daily Mac craft, Claude DevTools is the observability pane you will eventually install anyway, better to install it before the first mysterious Max invoice or the first baffling wrong refactor you cannot explain to a teammate.