Launched this week

Burnstate
Claude Code, Codex & Cursor limits, paced in your menu bar
120 followers
Claude Code, Codex & Cursor limits, paced in your menu bar
120 followers
Burnstate is a native Mac menu bar app for people who code with AI. It shows your Claude Code, Codex, Cursor and Vercel AI Gateway limits, marks how much of each window has passed, and tells you when you'd run out at your current pace. Answer Claude Code permission prompts and questions from a card, see every session's tokens and cost, take breaks that count only time away, and share a year of usage as a link. No account, no analytics.




Payment Required
Launch Team / Built With

AWS Startup AdvisorPersonalized AWS guidance that meets you where you’re already building
Promoted



The pace tick is what sold me — '60% used' never tells me if I'm actually in trouble, but fill vs. time passed does at a glance. I hit the Claude Code wall mid-task too often, usually right in the middle of a big refactor, so having that in the menu bar before I start something long is exactly the check I'd want. Congrats on the launch — the no-account, local-logs approach is a nice touch too.
@jcbuilds Thank you, JC! That's exactly the moment we built it for: a big refactor, everything flowing, and then the wall. Glad the pace tick clicks for you, it changed how we plan our own sessions too. And thanks for noticing the local-first part, keeping it on your Mac with no account mattered a lot to us. Congrats on Haplo AI as well, offline and private is a great direction 🙌
Measuring the limit against the clock is the right framing. A good share of my Claude Code usage comes from headless claude -p jobs started by cron, not from an open terminal. Do those runs show up in Sessions and count toward the pace forecast too?
@jindrich_regal Thanks! Good news on both:
Pace forecast: yes. The limits come straight from your Anthropic account, so every run counts, including headless claude -p jobs from cron, even ones on other machines.
Sessions: yes, as long as the run writes a transcript, which claude -p does by default (unless you pass --no-session-persistence). Finished runs show up in Sessions with their tokens and cost, and they count toward Today and your burn report too.
Two notes: Burnstate reads the default Claude config folders (~/.claude and ~/.config/claude), so if your cron jobs use a custom CLAUDE_CONFIG_DIR, those logs won't be picked up. And Sessions shows the last 24 hours, so a very busy cron can crowd the list. If that's your setup, we'd love to hear how you'd want those runs grouped.
we run like 5 claude code sessions in parallel and the 5h wall always lands mid task, so the pace tick is honestly what I wanted lol
@digi_dinos Ha, 5 at once is exactly who we built it for 😄 The tick tells you early when you’re running ahead, and Burnstate also shows when you’d hit the wall at this pace, so you can wrap up or pause a session before it dies mid-task. And we’re working on the next step: resuming a session automatically once the 5h window resets. Thanks for trying it!
@yozhef auto resume would be the big one for us tbh. the pause itself is fine, it's coming back and working out where each session left off that eats the time
@digi_dinos Totally get it, the “where was I in each of these” part is the real cost. Until auto resume lands, two things in Burnstate help: each session has a short AI summary of what it did, and a “copy resume” line that reopens it in the right folder. Quick question so we build it right: would you want it to just continue on its own after the reset, or come back with a summary first so you can confirm?
@yozhef summary first for sure. half the sessions that hit the wall were right before something I'd want to look at anyway lol. thanks for following up, good luck with it 🙌
Putting the elapsed window beside the usage percentage makes the number easier to interpret. Seeing the remaining time and current pace together would help someone decide whether to start another long task.
@oleksii_sekundant Exactly the decision we had in mind! Every limit in Burnstate shows how long until it resets, how far ahead or behind the clock you are (like "22% ahead"), and, when you're burning fast, roughly when you'd run out. So before a long task you can tell at a glance whether this window will hold or it's better to wait for the reset. Thanks for the kind words 🙏