Claude DevTools
The missing DevTools for Claude Code. Reads session logs and reconstructs a visual timeline of every file read, tool call, diff applied, and token consumed. Local desktop app, read-only.
- See a visual timeline of every file change Claude made
- Track token usage and cost across your coding sessions
- Debug unexpected behavior by reviewing the action history
Finally, observability for Claude Code sessions. See exactly what Claude did, how many tokens it burned, and which files it touched — without modifying Claude Code itself.
Developers who want to understand and optimize their Claude Code usage. Useful for debugging unexpected behavior, tracking token costs, and reviewing what Claude changed.
https://github.com/matt1398/claude-devtools
By matt1398
How to Get It
Trust Signals Automated Scan
Data & Access
Community Pulse Active
Discussed on Hacker News, Reddit
- Attention Vibe Coders: You are not helpful! — Reddit · 2495 pts
- Claude Code's CLI feels like a black box now. I built an open-source tool to see — Reddit · 891 pts
- Claude Code’s CLI feels like a black box. I built a local UI to un-dumb it, and — Reddit · 336 pts
16 mentions across 2 sources
Reviewer notes
Automated Scan review. These are observations, not a security certification.
Read-only tool. Only reads local session logs. No network calls. No modification of Claude Code. Available via brew cask.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.