Car dash for your Claude usage
A live dashboard for Claude Code usage limits, built like a car instrument cluster.
Try the live product
Context
I use Claude every day and the usage limits are real, but all the product gives you is a percentage, which does not tell you how fast you are burning through, which limit runs out first, or how long you have got.
My Role
All of it, solo: concept, research, data, design, UI, motion, copy, onboarding, the local helper on npm, the tests, the audits, QA and the deploy, built with Claude, Claude Code, Claude Design and ChatGPT.
Discovery & Research
I looked at car clusters from Porsche, Mercedes, Polestar and Audi and took two ideas, give people relative information they can act on (56 minutes at this pace, not 62% used) and let them notice things without staring. The data was the hard part, because Claude Code writes each response several times over and the source is blind 96% of the time, so everything dedupes before it counts.
What I Built
A car instrument cluster: your limits are fuel tanks, burn rate is the speedometer with a redline, context is the temperature gauge, and the big number tells you how long you have got and which limit stops you first. It is live now at nateheld.com/claude-dash with two ways in, a Demo that needs no setup and a Live mode that is one command, with no backend, no account and nothing uploaded.
Claude Code workflow
The full cluster with the demo timeline below it, events like cache miss, heavy work and window reset marked along the scrubber. Designing, building, testing, improving.
What Was Hard
Owning the whole thing end to end, especially the speed bumps, halfway in I hit a blocker I thought had killed the live version and pivoted before I found the way back. The fix was a small helper you install that reads the sign in Claude Code already saved, so real limits come back in about 200 milliseconds and only percentages ever reach the browser.
Burn rate
The burn-rate dial, drawn past its computed redline. Motion design over a data-driven redline.
What Happened
I audited it three ways over a real test suite, and one pass turned up a real security hole where the helper would have let any website read every Claude conversation on the machine. What shipped is a live product with a published npm package underneath it: 3,775 lines on the page with no dependencies, 598 in the helper, 251 tests and 27 more, 1.68 billion tokens spent (and usage consuming!).
Push start
The ‘system off’ start screen: push start to choose Demo or Live before anything is read or installed. Car-themed from the very start.
Want a full walkthrough?
Let's talk, I would love to show you how it actually works!