Open-Source Observability · matt1398

claude-devtools

claude-devtools is a free, open-source desktop application that reconstructs Claude Code's hidden execution details—file operations, tool calls, token usage, and subagent activity—by reading local session logs into a visual UI. It runs on macOS, Linux, Windows, and Docker with zero configuration.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/matt1398/claude-devtools

3.7k

GitHub stars

281

Forks

TypeScript

Primary language

MIT

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	matt1398/claude-devtools
Owner	matt1398
Primary language	TypeScript
License	MIT — OSI-approved
Stars	3.7k
Forks	281
Open issues	43
Latest release	v0.5.0 (2026-05-13)
Last updated	2026-05-13
Source	https://github.com/matt1398/claude-devtools

What claude-devtools is

Electron-based TypeScript desktop app that parses Claude Code session transcripts and logs stored in ~/.claude/, reconstructing context window attribution (7 token categories), tool call I/O, execution trees, and project memory layers. Exposes SSH remote session inspection and exports to Markdown/JSON/plaintext.

Quickstart

Get the claude-devtools source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/matt1398/claude-devtools.git2cd claude-devtools3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Debugging Claude Code Behavior

Inspect exact file paths, diffs, regex patterns, and tool outputs that the terminal summary hides. Track token consumption per-turn across multiple context categories to understand context window saturation.

Auditing Multi-Agent Workflows

Visualize nested agent execution trees with tool traces, token metrics, and cost breakdowns. Understand task delegation and subagent coordination without manual JSON parsing.

Optimizing Claude Code Projects

Review project memory layers (MEMORY.md + per-layer files), copy clean session transcripts, and export structured logs for analysis. Identify patterns in token usage and tool call sequences.

Implementation considerations

Installation is straightforward (Homebrew, direct DMG/AppImage, Docker); zero API key or credentials setup needed. Works immediately on existing Claude Code sessions.
Relies on Claude Code writing session logs to ~/.claude/ with expected schema; compatibility depends on Claude Code release version and log format stability.
Memory layer rendering assumes MEMORY.md frontmatter and .md files in ~/.claude/projects/<id>/memory/ directory; custom memory structures may not parse correctly.
SSH remote inspection requires SSH keypair or agent setup and assumes target machine has ~/.claude/ directory populated. Network latency may affect UI responsiveness.
Export formats (Markdown, JSON, plaintext) preserve content fidelity for sharing and analysis, but downstream tooling must handle Markdown frontmatter and nested structures.

When to avoid it — and what to weigh

Real-Time Monitoring Required — claude-devtools reads stored logs post-execution. It does not offer live streaming or real-time telemetry integration with Claude Code or external observability systems.
Non-Local Environments Only — Tool requires local access to ~/.claude/ or SSH tunnel to ~/.claude/. If Claude Code runs on ephemeral/containerized machines without log persistence or SSH access, inspection becomes impractical.
Production Monitoring at Scale — Designed for developer debugging, not enterprise telemetry aggregation. No centralized log ingestion, multi-user RBAC, or SLA instrumentation.
Strict API-Only Integrations — claude-devtools does not expose a public API for programmatic log access. Requires UI interaction or manual file parsing.

License & commercial use

MIT License. Permits free use, modification, and distribution in commercial and private projects, subject to including the license notice. No warranty or liability.

MIT is a permissive OSI license compatible with commercial use. You may use claude-devtools in commercial products and services without restriction, provided you retain the MIT license attribution. No commercial support, SLAs, or warranties are implied by the license.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Strong
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Good
Assessment confidence	High

Security considerations

claude-devtools reads local session logs and Claude Code system prompts stored unencrypted in ~/.claude/. No encryption at rest or in transit for local file access. SSH remote sessions use standard SSH authentication (keypair or agent); ensure SSH keys are protected and ~/.ssh/config security is maintained. Electron app inherits Chromium rendering engine security model; keep Electron dependency updated. No explicit audit trail or compliance (HIPAA, SOC2, etc.) claimed.

Alternatives to consider

Claude Code --verbose flag + manual JSON parsing

Native alternative; dumps raw logs including system prompts and internal state. Labor-intensive, poor UX; no visual context reconstruction, filtering, or structured export.

Anthropic Console (web-based) with API logging

If using Claude API directly (not Claude Code extension), web console offers token attribution and tool call logs. Requires API usage instead of local Code sessions; does not capture Code-specific tool traces or subagent trees.

Custom log parsing scripts + UI (Dash, Streamlit, etc.)

Full control over log schema, export formats, and integrations. Requires substantial engineering effort and ongoing maintenance as Claude Code log format evolves.

Software development agency

Build on claude-devtools with DEV.co software developers

Download claude-devtools today to inspect session logs, debug tool calls, and optimize token usage. Free, open-source, zero configuration. Available for macOS, Linux, Windows, and Docker.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Claude-Code-Usage-Monitor SysmonTools opcode

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Observability AI Application Development Custom Software Development Talk to DEV.co

claude-devtools FAQ

Does claude-devtools send my session logs or prompts to Anthropic or any external server?

Based on the README, it reads logs stored locally in ~/.claude/ or over SSH to a remote ~/.claude/. No upload or cloud integration is documented. Privacy/security notes mention logs remain on-device, but review the privacy policy on claude-dev.tools for formal guarantees.

Will claude-devtools work with future Claude Code releases?

Compatibility depends on session log schema stability. If Claude Code changes the format or location of ~/.claude/ logs significantly, claude-devtools may break. Active maintenance suggests the author will track updates, but no explicit compatibility guarantee is stated.

Can I export session logs for compliance or audit purposes?

Yes, UI offers export to Markdown, JSON, and plaintext. Exports preserve tool call details, context attribution, and memory layers. Ensure exported data is handled per your data governance policy (no automatic redaction of sensitive prompts/outputs documented).

Is there an API or programmatic way to fetch session data?

Not documented. Tool is UI-driven. For programmatic access, you would parse ~/.claude/ files directly or contribute API support to the project.

Software developers & web developers for hire

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If claude-devtools is part of your open-source observability roadmap, our team can implement, customize, migrate, and maintain it.

Gain Visibility into Claude Code Sessions

Download claude-devtools today to inspect session logs, debug tool calls, and optimize token usage. Free, open-source, zero configuration. Available for macOS, Linux, Windows, and Docker.

Talk to DEV.co Schedule a Consultation