Claude Code usage in your menu bar, not another browser tab
If you run Claude Code every day, you know the interruption: mid-refactor, you wonder how much of your rolling window is left, open a dashboard, lose your flow, and come back hoping you weren't already at 94%. Anthropic enforces limits that rarely line up with how you work: a 5-hour rolling window, an overall weekly cap, and per-model weekly limits on top. None of them shows up next to your editor unless you go looking.
Every clock, one glance
Token Gauge is a small, native menu-bar app for Mac. The same app, on the same licence, runs in the Windows system tray and on Fedora. It reads Claude Code's usage on your machine and shows live 5-hour and weekly percentages, color-coded green, amber or red, plus a countdown to the next reset in your local timezone. Since v1.1 each model's own weekly limit gets its own bar too, a separate Fable weekly gauge, for example, because a model's cap can run dry days before your overall week does. Pin Claude as your primary agent and the menu bar shows the number that matters without opening the popover at all.
What you get for Claude Code
The free tier needs no licence key or Token Gauge account. It includes Claude's overall 5-hour and weekly percentages, both reset countdowns, and default alerts at 80% and 95%. Lifetime adds each model's weekly limit, per-model token and cost history, pace and rate deltas, configurable alert thresholds, reset alerts and quiet hours. Heads up: this works on Claude Pro, Max, Teams, Enterprise and the Console. The free claude.ai plan has no usage endpoint, so it reads blank.
Local reads, honest scope
We're explicit about what Token Gauge does and doesn't do. It reads usage from Anthropic's own authenticated usage endpoint using credentials already on your system, and it never touches your repositories, prompts or conversation logs. That read is authoritative and doesn't consume any of your quota. The only network calls Token Gauge makes are each provider's usage endpoint, one licence check, and a signed check for app updates; it isn't fully offline, but your code and prompts never leave the machine because there's nowhere for that data to go.
Privacy in plain terms: Token Gauge asks Anthropic "how much have I used?" with credentials you already have. No analytics, no tracking pixels, no telemetry. It gives you visibility and timing. It does not raise your limits or change what you pay.
Claude Code, straight answers.
Anthropic meters Claude Code on a rolling 5-hour window: every message counts against it, and it resets 5 hours after your first message in that window, not at a fixed clock time. Token Gauge reads that window directly from Anthropic's usage endpoint and shows it as a live percentage, color-coded green, amber or red, with a countdown to when it resets in your local timezone.
Alongside the 5-hour window, Anthropic enforces an overall weekly cap. Token Gauge shows both overall percentages and reset countdowns on Free. Lifetime also shows each model's own weekly limit as a separate bar, for example Fable, because a model's cap can run out days before the overall week does.
No. Token Gauge is a meter, not a booster. It shows your usage and reset timing so a limit never surprises you mid-task. It does not raise your 5-hour window, add weekly quota, unlock higher per-model limits, or change what you pay Anthropic. Anthropic sets and controls every limit; Token Gauge only reads and displays it.
Yes. Free includes Claude's overall 5-hour and weekly percentages, reset countdowns, and default 80% and 95% threshold alerts, with no licence key or Token Gauge account required. The $11.99 Lifetime licence adds per-model Claude weekly limits, history, pace and deltas, configurable thresholds, reset alerts, quiet hours, and tracking for Codex, Cursor, Copilot and Antigravity.
Not for usage data. Token Gauge reads Claude Code's usage from Anthropic's authenticated usage endpoint, which is only available on Claude Pro, Max, Teams, Enterprise and Console plans. The free claude.ai plan has no usage endpoint, so those fields read blank. This is an Anthropic limitation, not something Token Gauge can work around.