Live token burn
Input, output, cache read, cache write — broken out and updated as Claude works. No more guessing the bill.
Building in public · v0.0.1
A VSCode extension that surfaces what Claude Code is doing — token burn, files touched, persistent memory — without leaving your editor.
Phase 1 ships read-only sidebar + status bar. Phase 2 adds mode toggles, MCP health, and an embedded claude-office panel.
Input, output, cache read, cache write — broken out and updated as Claude works. No more guessing the bill.
Every Edit / Write / MultiEdit Claude has run this session, with click-to-open. Audit the diff at a glance.
Your MEMORY.md entries listed inline. Click any line to open the underlying memory file.
Workspace, token total, file count — always visible. The cockpit you didn't know you needed.
Claude Code already touches everything sensitive on your machine. A tool that surfaces its state has no business phoning home.
fetch, http, or XMLHttpRequest in the source. Grep it yourself.~/.claude/. Only readFileSync, readdirSync, statSync, watch.~/.claude/projects/<encoded-cwd>/ and its memory/MEMORY.md.default-src 'none'; connect-src 'none'; form-action 'none'.Open source. Read the full privacy policy or audit the source.
Claude Code stores rich state on disk: session JSONL, persistent memory, hooks, MCP config. The CLI surfaces almost none of it. Cockpit reads what's already there and gives you a passive HUD instead of tail -f.
It's read-only by design in v1 — Claude Code is the source of truth. Cockpit just makes the truth visible.
git clone https://github.com/sboghossian/claude-cockpit.git
cd claude-cockpit
npm install
npm run compile
Then open in VSCode and press F5.