CodeBurn vs ccusage
CodeBurn and ccusage both track AI coding token usage and cost by reading the session files already on your machine, and both are free and open source. ccusage is a lean CLI focused on Claude Code. CodeBurn covers 31 tools, Claude Code, Cursor, Codex, Copilot, Gemini and more, and adds a macOS menu bar app and a local web dashboard on top of the CLI. Pick CodeBurn if you use more than one AI coding tool or want a visual dashboard; pick ccusage if you only use Claude Code and want the leanest possible CLI.
Side by side
| CodeBurn | ccusage | |
|---|---|---|
| Tools tracked | 31 (Claude Code, Cursor, Codex, Copilot, Gemini, and more) | Claude Code (plus a growing set) |
| Interface | CLI, macOS menu bar app, and web dashboard | CLI |
| Breakdown | By model, project, task, and tool | By model and project |
| Cache pricing | Correct (writes 1.25x, reads 0.1x) | Correct |
| Platforms | macOS, Linux, Windows | macOS, Linux, Windows |
| Local & private | Yes, nothing uploaded | Yes, nothing uploaded |
| Price | Free, open source | Free, open source |
When to choose CodeBurn
You run more than one AI coding tool and want a single view of all of it. You want a menu bar app or a dashboard instead of only terminal tables. You care about where the spend goes, by task type, not just the total.
When ccusage is the better pick
You only use Claude Code and just want a fast, minimal CLI report. ccusage is excellent at exactly that, and it is what got a lot of developers paying attention to AI coding cost in the first place.
Try CodeBurn
One command, fully local, no signup. See your real numbers in about ten seconds.