claude-devtools is a desktop application that reconstructs exactly what Claude Code did by reading the raw session logs already on your machine. It doesn't run or modify Claude Code but instead analyzes the session logs stored in ~/.claude/ directory to provide comprehensive visibility into Claude Code's activities.
The application features context reconstruction with per-turn token attribution across 7 categories including CLAUDE.md files, skill activations, @-mentioned files, tool I/O, thinking, team overhead, and user text. It includes a tool call inspector with syntax-highlighted Read calls, inline Edit diffs, Bash output, and full subagent execution trees. The tool also provides team and subagent trees with isolated execution trees per agent, notification triggers for alerts on .env file access and other events, SSH remote sessions capability, command palette search, and multi-pane layout for comparing sessions.
claude-devtools works by reading the session logs that Claude Code already writes to ~/.claude/ directory on your machine. It reconstructs everything the CLI hides without requiring any API keys or configuration, working with every session you've ever run from any tool.
The benefits include comprehensive visibility into Claude Code's activities, structured searchable data, and the ability to see exactly what was in the context window at any point during execution. It helps developers understand what files were accessed, what patterns were searched, what changes were made, and what commands were executed.
The tool is designed for developers using Claude Code who need detailed visibility into their AI coding sessions. It supports macOS, Windows, and Linux platforms and can be deployed via Docker with browser UI access.
admin
claude-devtools is designed for developers using Claude Code who need detailed visibility into their AI coding sessions. It targets programmers and software engineers who want to understand exactly what Claude Code is doing during their development workflow, including which files are being accessed, what tools are being called, and how context is being managed throughout the session.