Claude Code Weekly Limits +50% Through July 13, 2026: Live for Pro, Max, Team, and Seat-Based Enterprise
Anthropic increased Claude Code weekly limits by 50% on May 13, 2026, through July 13, 2026. The lift is live now for Pro, Max, Team, and seat-based Enterprise users. It comes about a week after Anthropic doubled five-hour rate limits on the same plans and removed peak-hours limit reduction for Pro and Max -- so the practical headroom for heavy Claude Code users is materially larger than it was in early May.
Anthropic increased Claude Code weekly limits by 50% on May 13, 2026, now through July 13, 2026. The lift is live for Pro, Max, Team, and seat-based Enterprise users. The exact wording from the official ClaudeDevs post:
Claude Code weekly limits are increasing 50%, now through July 13. Live now for all Pro, Max, Team, and seat-based Enterprise users.
It comes about a week after Anthropic doubled five-hour rate limits and removed peak-hours limit reduction on the same plans. The practical headroom for heavy Claude Code users today is materially larger than it was at the start of May.
For context on what's been shipping in Claude Code itself, see Claude Code 2.1.133's worktree.baseRef and MCP OAuth proxy fixes and the spring quality post-mortem -- both are relevant context for how Anthropic is currently iterating on the product.
Key Takeaways
- +50% weekly limits, live now, through July 13, 2026 -- a 61-day window from the announcement.
- Plans covered: Pro, Max, Team, seat-based Enterprise. Not usage-based / API.
- Time-boxed. Expires July 13, 2026, unless Anthropic extends or replaces the policy.
- Stacks with the May 5-6 changes: five-hour rate limits doubled and peak-hours limit reduction removed for Pro/Max on Claude Code.
- No published absolute numbers. Anthropic describes both changes proportionally; check your own usage dashboard for the baseline.
- Affects weekly ceilings, not short-window bursts. The May 5-6 change is what addresses burst throttling; this is the weekly cap.
What the Official Sources Actually Say
The ClaudeDevs post is the authoritative source for this specific change. Two facts are explicit:
- The increase is 50%, applied to weekly limits.
- The window ends July 13, 2026 -- the post's wording is "now through July 13."
It is not a permanent policy change. If you build workflows that depend on the higher ceiling, plan for them to revert on July 14 unless Anthropic announces an extension or a permanent re-quota before then.
What "Weekly Limits" Means in This Context
Claude Code limits operate at two layers:
- Short-window (five-hour) rate limits, which gate how much you can do in any rolling five-hour stretch.
- Weekly limits, which cap total usage in a seven-day window.
The May 13 change applies to the weekly layer. The May 5-6 change applied to the five-hour layer (and removed peak-hours reduction on Pro/Max). They address different problems: bursts versus aggregate weekly consumption.
What the Earlier May 5-6 Change Did
Anthropic's earlier "Higher limits" announcement covered:
- Doubling Claude Code five-hour rate limits for Pro, Max, Team, and seat-based Enterprise plans.
- Removing peak-hours limit reduction for Claude Code on Pro and Max.
That earlier post does not describe the 50% weekly bump or the July 13 end date -- those are specific to the May 13 ClaudeDevs post. Treat the two announcements as additive policies, each documented separately.
How the Two Changes Stack
| Layer | Pre-May 5 | May 5-6 change | May 13 change | Net effect today |
|---|---|---|---|---|
| Five-hour rate limit | Baseline | 2x for Pro/Max/Team/seat-Enterprise on Claude Code | No change | 2x burst headroom |
| Peak-hours reduction | Applied on Pro/Max | Removed for Claude Code on Pro/Max | No change | No peak-hours throttling on Claude Code |
| Weekly limit | Baseline | No change | +50% through July 13, 2026 | 1.5x weekly ceiling through July 13 |
| Plans affected | -- | Pro, Max, Team, seat-Enterprise | Pro, Max, Team, seat-Enterprise | Same plan set |
Two compounding lifts on different layers: bursts and weekly ceiling. The combined effect for a heavy user is larger than either alone.
How a Reader Uses This Window
The 61-day window (May 13 through July 13, 2026) is enough time to materially change a few categories of work, then plan a soft landing back to baseline:
- Context-heavy refactors. Large repos with deep Read passes and multi-agent Plan + Execute sessions consume a lot of weekly tokens. Move ones you've been deferring into this window.
- Multi-day subagent workflows. Subagent fan-out adds up fast on the weekly meter. The 50% lift makes those workflows comfortably under cap.
- Spike weeks. A release crunch or migration that would have pushed against the weekly cap can be absorbed within the lifted ceiling.
- Experimentation. Cheaper experimentation cost lets teams try patterns (different effort levels, different subagent topologies, custom hook scripts) without paying for them out of normal weekly budget.
The thing to avoid: building permanent workflows that only fit inside the +50% window, then discovering on July 14 they no longer fit. Treat the lift as runway, not as the new baseline.
When to Choose Claude Code vs. Other Tools This Quarter
The temporary lift changes the per-task economics of Claude Code specifically, not Codex or Cursor. If you've been splitting work across multiple AI coding tools partly to manage Claude Code quota:
| Situation | Suggestion through July 13 |
|---|---|
| You hit weekly limits often on Claude Code | Consolidate more work back into Claude Code while the lift is active |
| You hit five-hour limits often | Already addressed by the May 5-6 change; the May 13 change is unrelated |
| You're on the API / usage-based tier | The promo does not apply; no change to your usage economics |
| You're on Free | Not eligible; the promo lists Pro, Max, Team, seat-Enterprise |
| You're on seat-based Enterprise | The lift applies; coordinate with your admin if your org has additional internal caps |
For a comparison anchor across tools, our Codex CLI vs Claude Code vs Cursor architecture piece is the broader frame, and the recent 2.1.133 release coverage captures what's been shipping in the product itself.
Caveats
- No absolute numbers published. Anthropic describes the change as a percentage. Your own usage dashboard is the source for raw caps.
- Window ends July 13, 2026. Plan accordingly. Re-test any workflow you wedge into the lift well before the expiry.
- Plan set is specific. The lift applies to Pro, Max, Team, and seat-based Enterprise -- not to API-billed or usage-based access. Free is not listed.
- No competitive commentary. Anthropic positions this as a customer-facing capacity adjustment; we are not speculating about what motivated the timing.
FAQ
See structured FAQ in the schema header for question-level details: what changed, which plans, permanence, how it stacks with the May 5-6 changes, raw numbers, and practical implications.
Sources
- ClaudeDevs official post: https://x.com/ClaudeDevs/status/2054639777685934564 (3:07 PM, May 13, 2026)
- Anthropic "Higher limits" news post: https://www.anthropic.com/news/higher-limits-spacex (context for the earlier five-hour and peak-hours changes; does not state the 50% weekly promo or end date)
Frequently Asked Questions
What changed on May 13, 2026?
Anthropic increased Claude Code weekly limits by 50%, now through July 13, 2026. The exact wording from the official ClaudeDevs post: 'Claude Code weekly limits are increasing 50%, now through July 13. Live now for all Pro, Max, Team, and seat-based Enterprise users.' Posted 3:07 PM, May 13, 2026.
Which plans get the increase?
Pro, Max, Team, and seat-based Enterprise. ClaudeDevs called them out by name. Usage-based or API-billed access is not part of this promo -- it applies to seat/plan-based Claude Code usage.
Is this a permanent change or temporary?
Temporary. The official wording is 'now through July 13' -- this is a window-limited lift, not a permanent re-quota. After July 13, 2026, weekly limits return to their prior level unless Anthropic extends or replaces the policy.
How does this stack with the doubled five-hour rate limits announced in early May?
It is additive. On May 5-6, 2026, Anthropic announced it was doubling Claude Code five-hour rate limits for Pro, Max, Team, and seat-based Enterprise plans and removing peak-hours limit reduction for Claude Code on Pro and Max. That earlier change addressed short-window throttling. This newer change lifts the weekly cap by 50% through July 13. Together: more burst headroom in any five-hour window AND a higher weekly ceiling.
What were the actual numerical limits before and after?
Anthropic did not publish absolute numbers in either announcement. The May 5-6 'higher limits' news post and the May 13 ClaudeDevs post describe the changes as percentages (doubled, +50%) and as policy removals (no peak-hours reduction). Use your own historical usage dashboards as the baseline -- the proportions are what's documented, not the raw caps.
What should heavy Claude Code users do with this window?
Two practical implications. First, multi-day or context-heavy workflows (subagents, long Plan + Execute sessions, large repos with extensive Read passes) have meaningfully more headroom for the next two months. Second, the lift expires July 13, so workflows that only fit inside the +50% should be re-planned before then -- not after -- to avoid a hard quota hit when the policy reverts.