Alternatives
Products that do what I put my Claude Code rate-limit burndown in the status line does
- 1

- 2

- 3

- 4CA
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…
Apr 2026 · github.com
- 5ID
2016 · codepen.io
- 6

- 7IB
May 2026 · github.com
- 8CC
Continuous Claude is a CLI wrapper I made that runs Claude Code in an iterative loop with persistent context, automatically driving a PR-based workflow. Each iteration creates a branch, applies a focused code change, generates a commit, opens a PR via GitHub's CLI, waits for required checks and reviews, merges if green, and records state into a shared notes file. This avoids the typical stateless one-shot pattern of current coding agents and enables multi-step changes without losing intermediate reasoning, test failures, or partial progress. The tool is useful for tasks that require many…
Nov 2025 · github.com
- 9IB
2019 · tillypay.com
- 10

Ask Claude Code where your usage went. Token audit, limit diagnosis and usage forensics — built from the session logs already on your machine, nothing leaves it. - kelviq/tare
10d ago · github.com
- 11IT
I hit my Claude Code usage limit yesterday in the middle of regular work. Not doing anything unusual - just a couple of coding sessions. It felt like it came out of nowhere. Then today Anthropic announced they're tightening 5-hour limits during peak hours. It feels like a rug pull is coming and we're all just supposed to accept "you've used too much" with no explanation of what "too much" means. Usage limits have always been opaque. A vague percentage bar. No dollar figure. No formula. No way to plan your work around it. So I built a proxy that captures the rate-limit headers Anthropic sends…
Mar 2026 · github.com
- 12IL
2014 · goreturnme.com
- 13

- 14

All status line renderings are captured from live sandbox containers under various scenarios. Anyone can submit a status line, and each one is manually reviewed before approval. Source: https://github.com/NathanAB/statuslin.es Enjoy!
20d ago · statuslin.es
- 15

Know when you'll hit your Claude limit — not just how much
Jul 2026 · chromewebstore.google.com
- 16II
2016 · github.com
- 17CW
Claude Code added a /stats command. The stats are cached in $HOME/.claude, so I made a fun program with Bun + WASM that pulls the stats (nonsensitive, nonidentifiable), posts them to a database, and lets you see where your usage lies. The code is here[^1] if anyone's interested in the rendering code or wants to make sure I'm not exfiltrating their credit card. [^1]: https://github.com/tspader/claude-wrapped/
Dec 2025 · spader.zone
- 18
A real-time statusline engine for Claude Code (+ elsewhere)
Mar 2026 · jamesprnich.github.io
- 19IM
Jan 2026 · github.com
- 20

- 21CF
Anthropic's usage analytics dashboard is only available to Team and Enterprise org admins. On a Pro or Max plan all you get is /usage and the claude.ai usage page, which show where you stand right now but not where you're heading. I looked at various open-source projects but none quite matched what I had in mind: an all-round control panel for Claude Code that's also a single binary, with no dependencies and no install steps. The other thing I cared about was forecasting the usage limits. Existing tools do burn-rate projections (ccusage) or percentile heuristics…
Jun 2026 · github.com
- 22IG
Mar 2026 · github.com
- 23
Cooked▲8Track Claude Code context usage in real time with NPC roasts
Jun 2026 · marketplace.visualstudio.com
- 24IB
Jul 2026 · chromewebstore.google.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →