Claude Max weekly window
Weekly usage jumped. You barely used it.
People on Max 20x keep reporting the same thing: the weekly meter was at a few percent after reset, then it jumped tens of points without a matching Claude Code session. Support and the model itself often cannot explain the gap between the 5-hour window and the weekly cap.
Usage HUD cannot rewrite Anthropic’s accounting. It can put the official weekly number, the 5-hour number, and the reset time in the Mac menu bar, each with a confidence label — official, high, medium, or manual — and a one-line reason. A stale official reading is labeled stale instead of looking live. That is the doctor: you know whether you are looking at the same endpoint as /usage, or at a number that has stopped updating.
If you only need Codex, CodexBar is free and you do not need this.
What to check before you panic
Is this the weekly cap or the 5-hour window?
Max still has both. Burning the 5-hour session does not always move weekly the way you expect, and weekly can move from other Claude surfaces on the same plan. If you only watch one number, the jump looks like a bug.
Is the number official?
Usage HUD reads the same usage endpoint Claude Code’s /usage panel reads. It does not refresh or change your token. If that endpoint says 50%, the meter is not inventing 50%. If the endpoint is quiet, the label says so.
Did another client spend it?
Claude Desktop, the web app, and Claude Code share plan windows. A jump that “wasn’t me in the terminal” is often another client on the same Max seat.
Buy Usage HUD
$9 USD · one time · personal license through 1.x
Apple silicon Mac, macOS 14+. Signed and notarized.
After you pay: the next page is your notarized .zip. Open it on your Mac. 14-day refund by email.
Launch price through 30 Sep 2026, then $15. If CodexBar already works for you, you do not need this.
Related
Claude Max 5-hour window · When ccusage stops tracking Claude · Usage HUD home