SaaS Metrics
Product Positioning & Context
Not another Claude Code GUI wrapper. claude-devtools doesn't run or modify Claude Code — it reads the raw session logs already on your machine and reconstructs everything the CLI hides. Every file path Read, every tool called, every diff Applied, every token consumed — structured into a visual timeline with per-turn context attribution, compaction visualization, subagent execution trees, and custom notification triggers. Works with every session you've ever run. Open source, runs locally.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is claude-devtools?
claude-devtools is a digital product or tool described as: See everything Claude Code hides from your terminal
Where did claude-devtools originate?
Data for claude-devtools was aggregated directly from the Product Hunt community ecosystem, representing raw developer and early-adopter sentiment.
When was claude-devtools publicly launched?
The initial public indexing or launch date for claude-devtools within our tracked developer communities was recorded on February 17, 2026.
How popular is claude-devtools?
claude-devtools has achieved measurable traction, logging over 144 traction score and facilitating 10 recorded discussions or engagements.
Which technical categories define claude-devtools?
Based on metadata extraction, claude-devtools is categorized under topics such as: Open Source, Developer Tools, Artificial Intelligence.
Are there open-source alternatives related to claude-devtools?
Yes, the GitHub ecosystem contains correlated projects. For example, a repository named 0xwilliamortiz/claude-red shares highly similar architectural descriptions and topics.
How does the creator describe claude-devtools?
The original author or development team describes the product as follows: "Not another Claude Code GUI wrapper. claude-devtools doesn't run or modify Claude Code — it reads the raw session logs already on your machine and reconstructs everything the CLI hides. Every file ..."
Community Voice & Feedback
I tried to download and use it, but as soon as I ran it, several errors started appearing in the popup nonstop: Tauri error, token error, tool usage error. I uninstalled the app and continued receiving error messages for almost 10 minutes.
wow this is exciting, even I am competitor from #19 place - still I upvote 200%
This will help me analyse exactly what Claude is doing when working with my MCP tools. Thank you!
This solves a real pain point. I've been using Claude Code heavily for my projects and the opacity of what happens under the hood has been driving me nuts - especially when debugging why it made certain file changes. The compaction visualization sounds super useful, I've had sessions where context gets silently dropped and I had no idea what it forgot. How well does it handle subagent sessions? I run nested agents pretty often and tracking what each one does is basically impossible from the terminal.
Hey PH! 👋 I built claude-devtools because I was frustrated with a specific problem: Claude Code stopped showing me what it's doing.
Recent updates replaced detailed tool output with opaque summaries — "Read 3 files", "Edited 2 files" — no paths, no content, no diffs. The context usage became a vague progress bar. The only alternative is `--verbose`, which dumps thousands of lines of raw JSON. There's no middle ground.
I shared this on Reddit as a weekend project to scratch my own itch, and the response was insane—over 100k views, 500+ upvotes, and 1,000+ downloads in just 48 hours. Clearly, we all hate coding blind! 😂
I tried every Claude Code GUI out there (Conductor, Craft Agents, Vibe Kanban, etc.). None of them solved this because they all *wrap* Claude Code. They inject prompts and only show sessions run through their own UI. If you ran a quick command in your terminal, it doesn't exist to them.
claude-devtools takes the exact opposite approach:
⚡ It doesn't touch Claude Code at all.
⚡ It just reads the raw session logs already sitting at `~/.claude/` and reconstructs the full execution trace.
Every file read (with syntax highlighting), every edit (with inline diffs), every tool call paired with its result, and every subagent's full execution tree.
🔥 The feature I'm most proud of is Visible Context Reconstruction: It reverse-engineers what's actually eating tokens in your context window, broken down across 7 categories per turn, showing exactly how context fills and compresses over a session.
It's 100% free, open source, zero network calls, and works on macOS/Linux/Windows/Docker.
What's your biggest frustration with the Claude CLI right now? I'd love to hear your thoughts, and I'll be here all day answering questions!
Recent updates replaced detailed tool output with opaque summaries — "Read 3 files", "Edited 2 files" — no paths, no content, no diffs. The context usage became a vague progress bar. The only alternative is `--verbose`, which dumps thousands of lines of raw JSON. There's no middle ground.
I shared this on Reddit as a weekend project to scratch my own itch, and the response was insane—over 100k views, 500+ upvotes, and 1,000+ downloads in just 48 hours. Clearly, we all hate coding blind! 😂
I tried every Claude Code GUI out there (Conductor, Craft Agents, Vibe Kanban, etc.). None of them solved this because they all *wrap* Claude Code. They inject prompts and only show sessions run through their own UI. If you ran a quick command in your terminal, it doesn't exist to them.
claude-devtools takes the exact opposite approach:
⚡ It doesn't touch Claude Code at all.
⚡ It just reads the raw session logs already sitting at `~/.claude/` and reconstructs the full execution trace.
Every file read (with syntax highlighting), every edit (with inline diffs), every tool call paired with its result, and every subagent's full execution tree.
🔥 The feature I'm most proud of is Visible Context Reconstruction: It reverse-engineers what's actually eating tokens in your context window, broken down across 7 categories per turn, showing exactly how context fills and compresses over a session.
It's 100% free, open source, zero network calls, and works on macOS/Linux/Windows/Docker.
What's your biggest frustration with the Claude CLI right now? I'd love to hear your thoughts, and I'll be here all day answering questions!
Discovery Source
Product Hunt Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.