Claude's weekly limit: all-models vs Sonnet vs Opus

On a Max plan and still ran out of Claude? There are actually two separate weekly caps that can trip you - and they produce completely different symptoms. One blocks everything; the other silently swaps Opus for Sonnet without telling you. Once you know which cap you hit, the path forward is obvious.

The short answer

Claude has three distinct rolling limits

Most users know about the 5-hour session cap - it is the one you hit mid-session that makes you wait a few hours. What catches people by surprise are the two weekly caps, especially because they run on different scopes and produce different user-visible effects.

Per Anthropic's usage limits documentation, the three caps are:

All three windows are rolling - they do not reset at midnight, on Monday, or at the start of the billing month. Each starts from your first relevant message of that particular cycle. This is covered in full in how Claude's usage limits really work in 2026 and confirmed by the community thread on Hacker News discussing why Claude's weekly limits don't reset every 7 days on a fixed schedule.

The two "I'm on Max and still ran out" scenarios

Here is the exact confusion that brings most Max plan users to this page. You pay $100 or $200 per month for a Max plan specifically to get more Claude capacity. Then you hit a wall anyway. Two very different things could be happening:

Scenario A - Claude is serving you Sonnet instead of Opus

You open a new chat, select Claude Opus, and send a message. The response comes back quickly but feels less capable than usual. Or you notice the model indicator in the UI quietly shows Sonnet rather than Opus. Or the responses on complex reasoning tasks are thinner than you expected.

This is the Opus-specific weekly cap. Claude downgrades you silently - there is no bold error message saying "Opus is unavailable." You just get Sonnet. Sonnet is still working and your overall weekly budget is not exhausted. You can still get work done; you just lose the extra capability of Opus until the rolling 7-day Opus window completes from when you first used Opus this cycle.

The Opus-specific cap is separate from your overall weekly pool. Exhausting it only affects Opus. Sonnet and Haiku continue to draw from the shared all-models budget, which may still have plenty of headroom.

Scenario B - Everything is blocked

You try Sonnet. You try Haiku. Nothing works. Claude shows a rate-limit or usage-limit message with a reset timestamp that is one to seven days in the future. This is the all-models weekly cap. Every model on your account is locked until the rolling 7-day window resets - even on Max 20x. This is a hard ceiling, not a soft downgrade.

Hitting the all-models weekly cap is rarer than hitting the Opus cap, especially on Max 20x. But it is possible if you run Claude Code heavily all week on large codebases, or if you drive many long agentic sessions. Anthropic does not publish the absolute budget numbers, so the only way to know how close you are is Settings > Usage on claude.ai, which shows the percentage consumed for each cap.

How to diagnose which cap you hit

The fastest diagnostic is a two-step test:

1. Open a new chat and explicitly select Sonnet. Send a simple message. If Sonnet responds normally, you have hit the Opus-specific cap only - your overall weekly budget is not exhausted. Skip to the Scenario A section above.
2. If Sonnet is also blocked, check the error message or the reset timestamp. A timestamp days away means you have hit the all-models weekly cap. If the timestamp is hours away, you may have hit the 5-hour session cap instead (much more common).

For a definitive reading, go to Settings > Usage on claude.ai. It displays separate progress meters for your session budget, your weekly all-models budget, and (on Max plans) your Opus-specific weekly budget. Each meter shows the percentage consumed and the reset timestamp. In Claude Code, run /usage in your terminal for the same data.

For a live, ambient view without opening any settings page, tokn.watch shows all three meters in your Mac menu bar as colored arcs that update in real time.

The rolling window - what "7 days" actually means

Both weekly caps use rolling 7-day windows, not calendar weeks. This is one of the most commonly misunderstood facts about Claude's limits.

The weekly all-models window starts when you send your first message of the cycle. If you sent that message on a Tuesday at 14:00, your weekly reset happens the following Tuesday at 14:00 - not Sunday night, not Monday morning. The same logic applies to the Opus-specific window: it starts from your first Opus message of that cycle.

The practical consequence: if you exhaust your weekly pool on a Thursday, you do not get it back Monday - you wait until the same time next Thursday. This is what the Hacker News thread on Claude's weekly limits documents in detail: users who expected a Monday reset discovered their window does not line up with any calendar boundary.

This also means your effective "weekly budget" per calendar month is not four equal blocks. Depending on when your cycle started, the number of complete windows per month varies by one. Heavy users who plan their Claude Code work around weekly capacity need to track the rolling timestamp, not assume Monday is the reset day.

How Max 5x and Max 20x change the budget

Max 5x gives approximately five times the budget of Pro across all three caps. Max 20x gives approximately twenty times. These are the multipliers Anthropic has publicly described; they do not publish the absolute usage-unit numbers for any plan.

What this means in practice:

• A Max 20x user doing the same weekly workload as a Pro user will hit the all-models cap roughly 20 times less often.
• The Opus-specific cap on Max 20x is also proportionally larger than on Max 5x, so Opus lasts longer before downgrading to Sonnet.
• But neither Max plan is unlimited. Very heavy Claude Code users - especially those running long agentic sessions on large codebases all week - can exhaust even Max 20x before the 7-day window closes.

According to Anthropic's usage limit best practices, the best way to stretch any plan's weekly budget is to match the model to the task - use Haiku for fast lookups, Sonnet for most coding work, and reserve Opus for tasks that genuinely require its reasoning depth. This extends the Opus-specific pool the most, since Opus burns budget fastest.

"Claude's usage limits are designed to provide fair access across all users. We recommend using the most appropriate model for each task rather than defaulting to the most capable model for every interaction." Anthropic - usage limit best practices (paraphrased)

The silent Opus downgrade in more detail

The Opus-specific cap downgrade is subtle enough that many Max users miss it for days. A few things to know about how it works:

• No hard error message. You are not shown "Opus is at limit." Claude simply starts responding as Sonnet. The model indicator in the UI updates if you look, but there is no proactive notification.
• Sonnet quality for Opus tasks. For most coding and writing tasks, Sonnet is nearly as good. For multi-step reasoning, long document analysis, or highly creative work, the quality gap is noticeable.
• Your overall weekly budget continues to deplete. Even in Sonnet fallback mode, your all-models weekly cap is still ticking down. Sonnet is more efficient than Opus per task, so your overall weekly pool lasts longer - but it is not paused.
• The Opus cap resets on its own timer. The Opus-specific window starts from your first Opus message of the Opus cycle, not your first message of the all-models cycle. They run on independent clocks.

For Claude Code users: the /usage command shows you the Opus pool percentage in addition to the session and overall weekly meters. Checking /usage before starting a heavy Opus-dependent agentic task tells you whether you have enough Opus budget to complete the task without mid-session downgrade.

How the session cap fits in

The 5-hour session cap is independent of the weekly caps. You can hit the session cap multiple times in a single week - each time you just wait a few hours before the session pool refills. It does not consume any of your weekly all-models budget when it is locked; the weekly clock keeps running, but the session cap is its own separate lockout.

The most confusing scenario: you hit the 5-hour session cap on a Friday afternoon, then the weekly all-models cap on a Friday evening. The session cap resets by midnight (5 hours from first message), but the weekly cap is still locked. You can send a message after the session reset, only to be told you are still at your weekly limit. The two caps compound independently.

A full comparison of all three caps and how they stack is in the deep dive on Claude's 5-hour session limit.

What to do when you hit each cap

If you hit the Opus-specific cap (Scenario A)

Keep working. Sonnet is a capable model for most tasks. Switch your default explicitly to Sonnet so you are not waiting for Opus responses that will just fall back anyway. Check Settings > Usage to see when your Opus window resets - it will be within 7 days of your first Opus message of the current cycle.

For future prevention: save Opus for tasks that genuinely need it. Use the model picker to default to Sonnet for exploratory coding, file reading, and drafting. Reserve Opus for the final reasoning pass on complex tasks. This extends your Opus pool across the full week.

If you hit the all-models weekly cap (Scenario B)

You have no Claude access until the rolling 7-day window resets. Check the reset timestamp in the error message or in Settings > Usage. If you need to keep working right now, the practical alternatives are Claude.ai's free tier (which runs on a separate pool), ChatGPT (different provider, completely independent limits), or a direct API call if you have an Anthropic API key with a separate billing quota.

For future prevention: track your weekly budget visually so you can see it depleting before it hits zero. The week-level budget runs on a 7-day clock - if you are at 80% by Wednesday, you are on track to exhaust it before the week-cycle ends. Slowing down or switching to lighter models mid-week preserves more capacity for time-sensitive tasks later in the week. The tactics in 13 ways to save Claude tokens apply equally at the weekly level.