What is claude-devtools CLAUDE.md?

A guide for claude-devtools, an Electron desktop app that shows how Claude Code sessions run.

Use it when developing, testing, formatting, type-checking, or investigating session and task data in the app.

It gives the coding agent the project’s technology choices, package-manager rule, commands, import paths, and locations of session data.

How matt1398/claude-devtools configures Claude Code

About the project

claude-devtools is a visual debugging application that reads Claude Code's locally saved logs and session transcripts and presents their hidden details. Developers use it to inspect tool inputs and outputs, file activity, token usage, subagents, context consumption, and team coordination. The catalogue entries add commands, hooks, agents, instructions, and settings for the tool.

matt1398/claude-devtools · 3,994 stars · on GitHub · claude-dev.tools

Reuse

Borrowing it

Nothing to install: this file belongs to matt1398/claude-devtools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/matt1398/claude-devtools/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/matt1398/claude-devtools

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/matt1398/claude-devtools/claude-md/github.svg)](https://agentmods.dev/instructions/matt1398/claude-devtools/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/matt1398/claude-devtools/claude-md"><img src="https://agentmods.dev/badge/instructions/matt1398/claude-devtools/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/matt1398/claude-devtools/claude-md"><img src="https://agentmods.dev/badge/instructions/matt1398/claude-devtools/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,595 This file is loaded in full into every session.

When invoked 1,595 The same file — it is already loaded in full.

Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.01595	$0.01595
Opus 5.5	$0.00638	$0.00638
Sonnet 5.5	$0.00319	$0.00319
Haiku 4.5	$0.00160	$0.00160

Measured 1mo ago against content hash 905e4bad3a46, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

claude-devtools CLAUDE.md scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf dist dist-electron node_modules

CLAUDE.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

claude-devtools

Electron app that visualizes Claude Code session execution

Tech Stack

Electron 28.x, React 18.x, TypeScript 5.x, Tailwind CSS 3.x, Zustand 4.x

Commands

Always use pnpm (not npm/yarn) for this project.

pnpm install - Install dependencies
pnpm dev - Dev server with hot reload
pnpm build - Production build
pnpm typecheck - Type checking
pnpm lint:fix - Lint and auto-fix
pnpm format - Format code
pnpm test - Run all vitest tests
pnpm test:watch - Watch mode
pnpm test:coverage - Coverage report
pnpm test:coverage:critical - Critical path coverage
pnpm test:chunks - Chunk building tests
pnpm test:semantic - Semantic step extraction tests
pnpm test:noise - Noise filtering tests
pnpm test:task-filtering - Task tool filtering tests

Path Aliases

Use path aliases for imports:

@main/* → src/main/*
@renderer/* → src/renderer/*
@shared/* → src/shared/*
@preload/* → src/preload/*

Data Sources

~/.claude/projects/{encoded-path}/*.jsonl - Session files ~/.claude/todos/{sessionId}.json - Todo data

Path encoding: /Users/name/project → -Users-name-project

Critical Concepts

isMeta Flag

isMeta: false = Real user message (creates new chunks)
isMeta: true = Internal message (tool results, system-generated)

Chunk Structure

Independent chunk types for timeline visualization:

UserChunk: Single user message with metrics
AIChunk: All assistant responses with tool executions and spawned subagents
SystemChunk: Command output/system messages
CompactChunk: System metadata/structural messages

Each chunk has: timestamp, duration, metrics (tokens, cost, tools)

Task/Subagent Filtering

Task tool_use blocks are filtered when subagent exists Keep orphaned Task calls (no matching subagent) for visibility.

Agent Teams

Claude Code's "Orchestrate Teams" feature: multiple sessions coordinate as a team.

Process.team? { teamName, memberName, memberColor } — enriched by SubagentResolver from Task call inputs and teammate_spawned tool results
Teammate messages arrive as <teammate-message teammate_id="..." color="..." summary="...">content</teammate-message> in user messages (isMeta: false). Detected by isParsedTeammateMessage() — excluded from UserChunks, rendered as TeammateMessageItem cards
Session ongoing detection treats SendMessage shutdown_response (approve: true) and its tool_result as ending events, not ongoing activity
Display summary counts distinct teammates (by name) separately from regular subagents
Team tools: TeamCreate, TaskCreate, TaskUpdate, TaskList, TaskGet, SendMessage, TeamDelete — have readable summaries in toolSummaryHelpers.ts

Read the full file on GitHub · 159 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 159 lines · 1,595 tokens per session scan C 905e4bad3a46

Subscribe to this mod's changes

claude-devtools CLAUDE.md is an instructions file published in the GitHub repository matt1398/claude-devtools (3,994 stars, last pushed 1mo ago), licensed MIT. It adds 1,595 tokens to every session, about $0.0064 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code ai ai-tools claude desktop-app developer-tools

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

claude-devtools: Instructions file for Claude Code