Usagebar

Usagebar

Track Claude Code Usage from your Menu Bar

155 followers

A macOS menu bar app that tracks your Claude Code 5-hour and weekly usage limits. See reset timers, get notifications, and never hit the wall unexpectedly.
Usagebar gallery image
Usagebar gallery image
Free Options
Launch Team / Built With
Unblocked AI Code Review
Unblocked AI Code Review
High-signal comments based on your team's context
Promoted

What do you think? …

Aryan Bhasin
Maker
📌
Hey PH! I built Usagebar to track your Claude Code usage from your menu bar, so you never hit limits mid-sprint. I've been using it daily for quick glances. Launching this as "Pay What You Want", would love feedback on future roadmap!
Chris Messina

Pay What You Want is appreciated, but it seems like maybe open sourcing with a FUNDING.yml approach might be better, given that @CodexBar is free and open source and offers more functionality:

El Pingüino

@chrismessina +1 to this, especially because it asking permission to keystorage.
However, i personal found usagebar asking permission for keystore less often, maybe because it doesn't track other models.

Aryan Bhasin

@elpinguinofrio correct, the app was designed to ask for your keychain permissions as little as possible (vs other apps that ask every few hours)

Aryan Bhasin

@chrismessina very cool, and I definitely didn’t know about FUNDING.yml (great idea).

Plan is to open source this too.

Ryan Thill

The scale pain here is quota truth: Claude Code has multiple windows (session and weekly), and if you rely on UI heuristics you can mis-predict resets or show “blocked” even when headers say allowed.

Best practice is to treat rate limit headers plus /usage output as source of truth, then compute timers from unified reset epochs and optionally reconcile against local JSONL usage logs for accurate history.

Are you parsing the anthropic-ratelimit-unified headers directly, and will you support multiple Claude accounts or teams so the menu bar can switch contexts without mixing limits?

Aryan Bhasin

@ryan_thill our app will show you the same limits as /usage. Includes both "session" and "weekly" limits.

We also, as you mentioned, use local .json logs as a fallback (and for API users).

Currently not supporting "teams" - the limits are for each individual user - but good idea.

Curious Kitty
You’re shipping a lightweight menu-bar utility, but users in this space often want deeper analytics (history, per-model breakdowns, budgets) and also care strongly about privacy. How are you prioritizing simplicity vs. power, and what principles will decide what you’ll never add?
Aryan Bhasin

@curiouskitty good suggestions, these will be on the roadmap. Priority was to ship something extremely lightweight first with a clean UX.

Chilarai M

Is it available in the App Store?

Aryan Bhasin

@chilarai currently available outside of App Store (faster to iterate on). It’s still signed with a developer account to distribute outside-of-app-store

Piroune Balachandran

Pay what you want is smart positioning here. SessionWatcher and CodexBar charge a few bucks, which adds friction when youre already paying $20-200/month for Claude. Curious if you pull from rate limit headers or just parse /usage output... the session vs weekly distinction matters when youre trying to time a reset around a big refactor.

Melvyn

great app!