Claude DevTools
Visualise and analyse Claude Code session executions
Quick Take: Claude DevTools
Claude DevTools is the most useful Claude Code companion for developers who want to improve their AI-assisted coding workflow. The conversation inspector explains Claude's decisions. Token analytics identify cost optimization opportunities. Session comparison turns prompt engineering into a measurable practice. The 4.1 rating reflects focused utility in a new and developing project. For developers who use Claude Code regularly and want to understand (not just use) their AI agent, Claude DevTools provides insights that make you a more effective Claude user.
Best For
- •Claude Code Users Who Want to Understand and Optimize Their Sessions
- •Developers Practicing Prompt Engineering with Measurable Results
- •Teams Tracking AI Coding Tool Costs and Effectiveness
What is Claude DevTools?
Claude DevTools is a companion application for Claude Code that lets you inspect, analyze, and compare your AI coding sessions in a graphical interface. While Claude Code runs in the terminal and produces a stream of actions (file reads, code edits, command executions), Claude DevTools presents that session data visually—conversation threads, tool call trees, token usage breakdowns, and side-by-side session comparisons. The core use case is understanding how Claude approached a task. After Claude Code finishes refactoring a module, Claude DevTools shows you the full session: what files Claude read first, what questions it asked itself, which tool calls it made, where it backtracked, and how many tokens each step consumed. This visibility helps you write better prompts—if Claude spent 60% of tokens reading irrelevant files, you know to narrow the context next time. The conversation inspector shows the full message exchange between you and Claude, including system prompts, user messages, assistant responses, and tool calls. Each tool call (file read, file write, bash command) is expandable with input/output details. You can see exactly what Claude saw when it read a file, what it wrote, and what command output it processed. For debugging unexpected behavior ('why did Claude modify that file?'), the conversation inspector provides the answer. Token usage analytics break down consumption by category: input tokens (context sent to Claude), output tokens (Claude's responses), and tool call tokens. Bar charts show which messages consumed the most tokens—often the initial codebase read is the biggest cost. Understanding token distribution helps optimize prompts: if context is the dominant cost, you can exclude irrelevant files; if output is the dominant cost, you can ask for shorter responses. Session comparison lets you run the same task with different prompts and compare the results side by side. Did prompt A produce better code than prompt B? Did it use fewer tokens? Did it take fewer steps? For developers refining their AI workflow, this is prompt engineering with actual data instead of guessing. Claude DevTools reads local session data from Claude Code—it doesn't make API calls, doesn't need your Anthropic API key, and doesn't send your code anywhere. It's a local analysis tool for understanding and improving how you work with Claude.
Install with Homebrew
brew install --cask claude-devtoolsDeep Dive: Prompt Engineering Through Session Analysis
How analyzing past AI coding sessions makes you a more effective prompt engineer.
History & Background
Prompt engineering emerged as AI models became powerful enough that the way you ask matters as much as what you ask. In AI coding agents, prompt quality directly affects output quality and cost. A vague prompt ('fix the bugs') might cause Claude to scan the entire codebase, using thousands of tokens, before finding the relevant files. A specific prompt ('fix the null pointer in src/auth/validate.ts line 42') goes straight to the target. Claude DevTools makes this difference measurable by showing token usage, step count, and approach for each session.
How It Works
Claude DevTools reads Claude Code's session data files (typically stored in ~/.claude/ or a similar directory). Each session is a structured log containing messages (system, user, assistant), tool calls (with inputs and outputs), token counts, and timestamps. Claude DevTools parses these files and presents them in a graphical interface with conversation threading, tool call trees, and analytics charts. The analysis runs entirely on your Mac—no network requests, no cloud processing.
Ecosystem & Integrations
The AI coding companion tools ecosystem is growing: Claude Island (real-time status), Claude DevTools (retroactive analysis), CodexMonitor (Codex CLI monitoring), and built-in analytics in Cursor and Windsurf. As AI agents become standard development tools, the analysis and optimization layer becomes important—not just using AI, but using it effectively. Claude DevTools positions itself as the 'profiler' for AI coding sessions, analogous to how Instruments profiles app performance.
Future Development
Expected improvements include AI-powered session analysis (automatic identification of inefficient prompting patterns), team dashboards for aggregate analysis, integration with Claude Code for inline suggestions ('this context scope could be narrowed to save 40% of tokens'), and support for comparing sessions across different AI models (Claude vs. GPT-4 for the same task).
Key Features
Conversation Inspector
View the full message exchange of any Claude Code session as a structured conversation thread. System prompts, user messages, assistant responses, and tool calls are displayed in order with expandable details. Each tool call shows its type (file read, file write, bash command), input (what file, what command), and output (file contents, command output). Click any message to see its token count. The inspector answers 'what did Claude see and do?' for any session.
Tool Call Visualization
A tree or timeline view of every tool call Claude made during a session. See the sequence of file reads, file writes, and command executions in chronological order. Color-coded by type (blue for reads, green for writes, orange for commands, red for errors). Click any tool call for details. This visualization reveals Claude's approach—did it read comprehensively then write, or did it write-test-iterate? Understanding the pattern helps you prompt more effectively.
Token Usage Analytics
Breakdown of token consumption by message type (system, user, assistant, tool call), by step (initial context load, code generation, test execution), and by model. Bar charts and pie charts show where tokens went. Historical charts show usage trends across sessions. The analytics help identify inefficiencies: if 70% of tokens go to reading files that don't get modified, narrowing the context scope would cut costs significantly.
Session Comparison
Compare two or more sessions side by side. Same task, different prompts—which produced better code, used fewer tokens, or took fewer steps? Or compare sessions over time—are you getting more efficient with Claude as your prompting improves? The comparison view shows metrics (token usage, step count, duration, files modified) and highlights differences in approach.
Export & Sharing
Export session data as JSON, Markdown, or HTML reports. Share a session analysis with a colleague to show how Claude approached a problem. Export token usage for expense tracking. The Markdown export creates a readable document showing the conversation, tool calls, and metrics—useful for documentation and post-mortems.
Session Library
Browse all past Claude Code sessions organized by date, project, and topic. Search sessions by content (find the session where Claude worked on authentication). Tag sessions for organization. The library grows as you use Claude Code, becoming a searchable history of AI-assisted work. For teams, this can serve as institutional knowledge—how Claude was used to solve specific problems.
Who Should Use Claude DevTools?
1Prompt Engineering Developer
A developer is refining their Claude Code workflow. They run the same refactoring task with three different prompts—one broad ('refactor auth module'), one specific ('refactor auth module: extract token validation into a separate function'), and one with context hints ('refactor auth module, focus on files in src/auth/, ignore test files'). Claude DevTools compares the three sessions: the specific prompt used 40% fewer tokens and produced cleaner code. They adopt the specific prompting style for future work.
2Developer Debugging Unexpected Output
Claude Code modified a file the developer didn't expect. Using Claude DevTools' conversation inspector, they trace Claude's reasoning: Claude read a config file that referenced the unexpected file, interpreted a dependency, and modified both files to maintain consistency. The tool call tree shows the chain of reads that led Claude to the second file. The developer understands the decision and adds the file to their prompt's exclusion list for future tasks.
3Team Lead Reviewing AI Usage
A team lead reviews session analytics across the team's Claude Code usage. They export weekly reports showing total tokens, average tokens per session, and cost per developer. One developer consistently uses 3x more tokens than others—review reveals they're not narrowing context scope. The lead shares a specific session comparison showing how scoped prompts reduce token usage by 50%, providing concrete training material.
How to Install Claude DevTools on Mac
Claude DevTools requires Claude Code and is available via Homebrew.
Install via Homebrew
Run `brew install --cask claude-devtools`. The app installs to your Applications folder.
Ensure Claude Code is Installed
Claude DevTools reads session data from Claude Code. Install Claude Code first if you haven't: `npm install -g @anthropic-ai/claude-code`.
Launch and Load Sessions
Open Claude DevTools. It automatically scans for Claude Code session data in the default directory. Past sessions appear in the session library. New sessions appear as Claude Code creates them.
Explore a Session
Click any session in the library to open it. The conversation inspector, tool call visualization, and token analytics load automatically.
Pro Tips
- • Start by analyzing a session where Claude's output surprised you—the conversation inspector explains why Claude did what it did.
- • Use session comparison with your next prompt optimization experiment. Same task, different prompts, measurable results.
- • Export a well-structured session as Markdown documentation of how Claude solved a complex problem.
Configuration Tips
Start with Token Analytics
Open your most recent session and look at the token breakdown. Identify the biggest cost center—is it context loading (reading many files), code generation (long responses), or iteration (multiple attempts)? This immediately tells you where prompt optimization will have the most impact.
Tag Sessions by Type
Tag sessions as 'refactoring,' 'new feature,' 'bug fix,' 'test writing,' etc. Over time, you can compare token usage by task type. Refactorings might cost 3x more than bug fixes, which helps with budgeting and deciding when to use Claude vs. coding manually.
Alternatives to Claude DevTools
AI coding session analysis is a new category with few dedicated tools.
Claude Island
Claude Island provides real-time status monitoring (is Claude working? is it done?). Claude DevTools provides retroactive analysis (how did Claude approach the task? where did tokens go?). They're complementary—Claude Island during sessions, Claude DevTools after sessions.
CodexMonitor
CodexMonitor provides real-time monitoring and cost tracking for Codex CLI sessions. It's analogous to Claude DevTools but for OpenAI's agent. CodexMonitor focuses more on cost alerts and budget management, while Claude DevTools focuses more on session analysis and prompt optimization.
Manual Log Reading
Claude Code writes session logs that you can read directly in a text editor. Claude DevTools structures this same data visually with conversation threads, tool call trees, and token charts. If you're comfortable reading JSON logs, you don't need Claude DevTools. If you want visual analysis, it saves significant time.
Pricing
Claude DevTools is free to download and use. No subscription, no premium tier, no data collection. All analysis runs locally on your Mac.
Pros
- ✓Conversation inspector shows exactly what Claude saw and did
- ✓Token analytics identify cost optimization opportunities
- ✓Session comparison enables data-driven prompt engineering
- ✓Tool call visualization reveals Claude's problem-solving approach
- ✓Export as Markdown creates documentation from AI sessions
- ✓All analysis runs locally — no data sent externally
Cons
- ✗Only works with Claude Code — doesn't analyze Codex CLI, Cursor, or other AI tools
- ✗New project with a developing feature set
- ✗Analysis is retroactive (after sessions) — no real-time monitoring
- ✗Session data can accumulate and use disk space over time
- ✗Limited team features — each developer analyzes their own sessions
Community & Support
Claude DevTools is part of the growing Claude Code ecosystem. The app's development is tracked through its website and GitHub repository. The Claude Code community on Reddit (r/ClaudeAI), Twitter/X, and Discord discusses workflow optimization, prompt engineering, and companion tools. As prompt engineering becomes a recognized skill, tools like Claude DevTools that provide measurable session data are increasingly valued.
Frequently Asked Questions about Claude DevTools
Our Verdict
Claude DevTools is the most useful Claude Code companion for developers who want to improve their AI-assisted coding workflow. The conversation inspector explains Claude's decisions. Token analytics identify cost optimization opportunities. Session comparison turns prompt engineering into a measurable practice. The 4.1 rating reflects focused utility in a new and developing project. For developers who use Claude Code regularly and want to understand (not just use) their AI agent, Claude DevTools provides insights that make you a more effective Claude user.
About the Author
Related Technologies & Concepts
Related Topics
AI Coding Agent Tools
Tools for AI-assisted coding and companion utilities.
Sources & References
Fact-CheckedLast verified: Feb 23, 2026
- 1Claude DevTools
Accessed Feb 23, 2026
Research queries: Claude DevTools Mac Claude Code analysis