CodeBurn
ProductivityLocal TUI dashboard tracking AI coding token spend across Claude Code, Cursor, Codex, and 25+ tools.
Install
$ npm install -g codeburn
Update
$ npm install -g codeburn@latest
Standalone npm CLI, not a copied skill dir; re-install globally to upgrade (or brew upgrade codeburn if installed via Homebrew).
When to use it
- You want to see where your AI coding tokens and dollars are going across Claude Code, Cursor, Codex, and other tools
- You need to audit or reduce AI coding spend and find waste (retries, re-reads, unused MCP servers)
- You want per-project, per-model, or per-task-type cost breakdowns without proxies or API keys
- You want to compare models on cost and efficiency, or correlate spend with git commits
Commands & flags
- codeburn
- Open the interactive 7-day token/cost dashboard.
- codeburn today
- Show today's usage summary.
- codeburn month
- Show usage for the current month.
- codeburn optimize
- Find spending waste and savings opportunities.
- codeburn compare
- Side-by-side model cost and efficiency metrics.
- codeburn yield
- Correlate sessions with git commits.
- codeburn export
- Export usage data as CSV or JSON.
How to use it
CodeBurn is a standalone command-line tool, not a Claude Code skill or plugin. It reads session data already on disk, so there is nothing to wire into Claude Code.
npm install -g codeburn # or: brew install codeburn, or: npx codeburn
codeburn # interactive 7-day dashboard
Common commands:
codeburn today # today's usage summary
codeburn month # current month
codeburn optimize # find spending waste / savings
codeburn compare # side-by-side model metrics
codeburn yield # correlate sessions with git commits
codeburn export # CSV/JSON export
Requires Node.js 22+ and at least one supported AI coding tool with local session data.
Why it earns its place
CodeBurn gives developers and teams granular, local-first visibility into AI coding spend, breaking costs down by project, model, tool, provider, MCP server, and task type while pricing every call via cached LiteLLM data. It runs entirely on local session files with no proxy or API keys, and its optimize, compare, and yield commands surface concrete waste and productivity signals. Not a skill itself, but a strong companion utility for managing Claude Code costs.