Show HN: CodeBurn – Analyze Claude Code token usage by task

112 points

2 months ago

Built this after realizing I was spending ~$1400/week on Claude Code with almost no visibility into what was actually consuming tokens.

Tools like ccusage give a cost breakdown per model and per day, but I wanted to understand usage at the task level.

CodeBurn reads the JSONL session transcripts that Claude Code stores locally (~/.claude/projects/) and classifies each turn into 13 categories based on tool usage patterns (no LLM calls involved).

One surprising result: about 56% of my spend was on conversation turns with no tool usage. Actual coding (edits/writes) was only ~21%.

The interface is an interactive terminal UI built with Ink (React for terminals), with gradient bar charts, responsive panels, and keyboard navigation. There’s also a SwiftBar menu bar integration for macOS.

Happy to hear feedback or ideas.

27 comments