Use when you want to see token consumption by task type, model, one-shot rate, or USD cost — observability dashboard for Claude Code sessions
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Reads directly from ~/.claude/projects/ (no API keys, no wrappers) and renders a TUI dashboard showing where tokens go.
Complementary to rtk: rtk reduces tokens spent (efficiency); codeburn shows which tasks need optimization most (observability). Together they close the feedback loop.
codeburn # Interactive TUI dashboard (keyboard navigation)
codeburn today # Today's sessions only
codeburn report -p 30days # 30-day rolling window
codeburn report --project <name> # Filter by project
codeburn export --format csv # Export for further analysis
codeburn export --format json # JSON output
| Metric | Why it matters |
|---|---|
| Tokens by task type (13 categories) | Find which work type is most expensive |
| One-shot rate per task type | % tasks done in 1 API call vs retry loop |
| Per-model breakdown | Cost difference between Opus and Sonnet for your actual tasks |
| USD cost estimate | Real spend per session / project |
| Input vs output token split | Output tokens cost 3-5× more than input |
refactor · bug-fix · feature · test · docs · review · debug · config · migration · research · security · cleanup · other
codeburn report → find low one-shot rate task type
→ add context/rules for that category in CLAUDE.md or claude/*.md
→ rtk reduces token output on those commands
→ re-run codeburn to verify improvement
Signal: If one-shot rate < 50% for a task type, it needs more upfront context or better rules.
npm install -g codeburn # Global install
npx codeburn # One-shot without global install
Requires Node.js 18+.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Route a codebase question to the right tool — structural graph, semantic search, or risk analysis. Use when you need to find or understand code without knowing exact file names.
The English summary is being prepared. Showing the original description.
Auto-configure CLAUDE.md and claude/ knowledge docs for a new project. Use when setting up Brain Bootstrap in a new repository. Discovers the codebase, fills in templates, and writes project-specific configuration.
The English summary is being prepared. Showing the original description.
Use before any new feature, component, or behavioral change — when you need to explore requirements and design before writing code
The English summary is being prepared. Showing the original description.
Activate safety guards for the session. Use /careful before critical operations — blocks rm -rf, DROP TABLE, git push --force, kubectl delete namespace, docker system prune via PreToolUse hook.
The English summary is being prepared. Showing the original description.
Generate a user-facing changelog from git commits — categorize, filter noise, translate to user language. Runs in isolated fork context.
The English summary is being prepared. Showing the original description.
Save session state before context gets full or before ending. Writes current task state, branch, and loaded docs to claude/tasks/todo.md so the next session can resume cleanly.
The English summary is being prepared. Showing the original description.