A CLI tool that reads Claude Code and Codex CLI session logs, quantifies token spend burned on idle turns, and shows per-session cost breakdowns devs can actually act on
Claude Code and Codex CLI ship with no native cross-session cost visibility. Devs spending $1,400+/week have zero built-in way to see where that money went. A community ecosystem filled the gap fast: Claude-Code-Usage-Monitor hit 8.2k GitHub stars and CodeBurn's HN launch (245 pts, 135 comments) found that 56% of spend goes to idle turns where the agent is waiting, retrying, or stalled. The existing tools surface totals but stop there. This CLI parses the raw session logs from both tools, classifies each turn as productive vs idle, ranks the sessions and workflows burning the most waste, and outputs a daily cost breakdown devs can use to cut their bill without changing their workflow.
Demand Breakdown
Social Proof 3 sources
Gap Assessment
3 tools exist (Claude-Code-Usage-Monitor, CodeBurn, ccusage) but gaps remain: No idle-turn classification. No cross-session history. No per-workflow breakdown. No Codex CLI support. Shows you the number but not what drove it or what to cut.; Single-session only. No real-time view. No daily/weekly trend. No actionable per-turn waste ranking. No Codex CLI support..
Features2 agent-ready prompts
Competitive LandscapeFREE
| Product | Does | Missing |
|---|---|---|
| Claude-Code-Usage-Monitor | Real-time token usage display for Claude Code with cutoff predictions and color-coded warnings. Shows running totals per session. | No idle-turn classification. No cross-session history. No per-workflow breakdown. No Codex CLI support. Shows you the number but not what drove it or what to cut. |
| CodeBurn | Post-session analysis of Claude Code token spend by task. Identified the 56% idle-turn finding. | Single-session only. No real-time view. No daily/weekly trend. No actionable per-turn waste ranking. No Codex CLI support. |
| ccusage | CLI that reads Claude Code local logs and displays aggregated token counts and cost estimates. | No idle vs productive turn classification. No waste ranking. No cross-tool support (Codex). Totals only, no actionable breakdown. |
Leads41BUILDER
Sign in to unlock full access.