I didn’t build TokenBar because I love dashboards.
I built it because I got tired of finding out about AI spending after the damage was already done.
The first time it hit me, I was deep in a solo-dev week: bouncing between my editor, Claude, and a couple of browser tabs trying to ship fast. Everything felt productive. Then the bill showed up and the number was bigger than my gut expected. Not catastrophic. Just annoying enough to make me realize I was flying blind.
That’s the part nobody talks about.
It’s not just the tokens.
It’s the silence.
You can feel a model getting useful. You can feel yourself leaning on it more and more. But unless you’re watching the cost in real time, the bill arrives as an argument with the past version of you.
I didn’t want another tab I’d forget to open.
I didn’t want another dashboard I’d check after the fact.
I wanted a tiny, always-there warning light sitting in the menu bar where I already live.
That’s why I built TokenBar: tokenbar.site
Not to make AI usage feel scary. Just to make it visible.
Because for solo devs, the real problem usually isn’t “AI is too expensive.”
It’s “I had no idea it was getting expensive until it already was.”
Once I could see token usage the same way I see memory or battery drain, my behavior changed immediately. I stopped spraying prompts everywhere. I started noticing which tasks were cheap, which ones were bloated, and where I was using a model because it was convenient instead of because it was worth it.
That’s the actual shift.
AI spend isn’t a monthly bill problem.
It’s a live feedback problem.
And if you build with AI every day, you probably need a better signal than a spreadsheet and a guilty feeling.
Top comments (0)