Usage limits
Claude weekly limit: what it means and when it resets
Last reviewed July 2026.
Short answer: The Claude weekly limit is a fixed ceiling on how much you can use Claude / Claude Code over a rolling 7-day account cycle. It sits on top of the 5-hour rolling window, so both apply at once. It resets on your weekly schedule — not on Monday — and the fastest way to hit it is a run of token-heavy agent sessions early in the week. Exact allowances vary by plan; verify against Anthropic’s current docs. As of July 2026, the shape below is stable.
Two limits, not one
Claude meters subscription usage with two clocks. The 5-hour window governs short-term intensity. The weekly limit governs the long game: a fixed ceiling across seven days that no amount of waiting-out-the-window will get around. You can be well within your 5-hour budget and still be blocked because the weekly cap is spent.
The hub for both clocks and the per-plan table is Claude Code usage limits. Max-specific headroom is in Claude Max limits.
Why you hit it by mid-week
The weekly cap is a token budget, and token-heavy work drains it out of proportion to the time spent. A single noisy afternoon — a build that dumps thousands of log lines into the context, an agent that re-reads the same files a dozen times, a long chain of tool calls — can eat a meaningful slice of the week, not just the day. Do that Monday and Tuesday, and Wednesday’s “weekly limit” or usage limit reached message stops feeling mysterious.
When it resets
| Clock | Reset | Waiting out the other clock |
|---|---|---|
| Weekly limit | Fixed 7-day cycle on your account | Waiting ~5 hours does not refill it |
| 5-hour window | Rolling after session start | Often clears the same day |
Whatever day your weekly cycle began is the day it refills. When you are capped, the product UI usually indicates which clock is blocking you and roughly when it frees up.
What happens when you hit it
When the weekly cap is spent, new Claude Code work pauses until the cycle resets. In practice you have three options: wait for the weekly reset, move up a plan tier (see Claude Max limits), or reduce how much each remaining session spends. Knowing which clock stopped you is the first step — a spent 5-hour window clears within hours; a spent weekly cap needs one of those three moves.
How to make it last
Because the weekly limit is about tokens, the way to stretch it is to spend fewer of them on the same work. Most waste falls into verbose tool output, files re-read across turns, and extra agent context — detail in Claude Code token usage.
The free hypermile-audit CLI reads your local transcripts and prints a plain-English breakdown of where your week’s tokens went. Nothing is uploaded; it is open source and runs on your machine. From there, Hypermile trims the noisy parts of each prompt before they reach the model.
Next steps
Run the audit below, then download Hypermile. For the full two-clock picture, start with Claude Code usage limits. Seeing the exact error string? Read usage limit reached.
Frequently asked questions
What is the Claude weekly limit?
It is a fixed ceiling on how much Claude / Claude Code usage you get over a 7-day account cycle on paid plans. It sits on top of the rolling 5-hour window, so both apply at once. Exact size varies by plan (Pro vs Max) and changes over time.
When does the Claude weekly limit reset?
It resets on a fixed 7-day cycle tied to your account, not on Monday of the calendar week. If your cycle rolls over on a Thursday, that is when the weekly allowance refills — regardless of how much of the 5-hour window you have left.
Why did I hit the Claude weekly limit before the daily one?
The weekly cap and the 5-hour window are separate clocks. You can stay under the 5-hour limit every day and still exhaust the weekly ceiling, because token-heavy sessions draw down the weekly budget faster than the short window refills.
Can I raise my Claude weekly limit?
A higher plan such as Claude Max carries a larger weekly cap, so upgrading raises the ceiling directly. Short of that, cutting tokens each session spends — noisy logs and repeated file reads — stretches the allowance you already have.