Claude Code Weekly Limits Are 50% Higher Through August 31: What Heavy Users Should Do

Anthropic quietly extended its Claude Code weekly limits promotion again. The 50% boost to weekly usage limits in Claude Code, originally set to expire in July, now runs through August 31, 2026. If you run Claude Code on a Pro, Max, or Team plan, your weekly allowance is 50% higher than normal right now, and you have roughly a week and a half left before it reverts. For heavy users who budget a full week around claude usage limits, this extension is free capacity, but only if you actually plan around it.

Here is what the extension means, what stays capped, and the exact moves worth making before the promotion ends.

The promotion: Claude Code weekly limits are up 50% until August 31

The change is simple. Since May 13, 2026, weekly usage limits in Claude Code have been 50% higher than the standard level on Pro, Max, and Team plans, and on legacy seat-based Enterprise plans. Anthropic has extended that end date more than once, and the current support page now states the increased weekly limits run through August 31, 2026 at 11:59 PM PT.

The 50% applies to Claude Code only, everywhere it runs: the CLI, IDE extensions, desktop, and the web. It applies automatically, so there is nothing to activate. You can run /usage inside the CLI to see the updated weekly allowance reflected live.

What the boost does NOT touch is worth reading twice, because it is where most people get burned:

• The 5-hour usage limits are unchanged. You can still hit the rolling 5-hour wall even with more weekly capacity.
• Claude products outside Claude Code, including Claude web, desktop, mobile, and Claude Cowork, keep their normal usage limits.
• Free plans and consumption-based Enterprise seats are excluded from the promotion entirely.

So the extension widens your weekly budget, not your short-horizon burst ceiling. That distinction matters for how you schedule month-end work.

What heavy users get from higher claude usage limits

The weekly limit is the number that actually governs how much sustained work you can push through Claude Code in a week. When it is 50% higher, you can run noticeably longer autonomous sessions, more parallel agent tasks, and heavier refactors before hitting the wall and being forced to wait out the reset or fall back to API pricing.

For a heavy user on a Max plan, that is meaningful capacity. The difference between a normal weekly allowance and a 50% bump is often the difference between finishing a large migration in one week versus watching it stall at the ceiling and spill into paid API usage or a second plan cycle.

This is also the moment to be precise about tiers. The promotion lifts the weekly limit on your plan by 50%, but it does not change the plan itself. A Max 5x weekly allowance with the boost is still a Max 5x allowance, just multiplied. It is not a free upgrade to the next tier. If your workload has outgrown your tier and you were leaning on marginal weekly overages, the extension gives you a short reprieve, not a permanent fix.

What changes after August 31

When the promotion ends, weekly usage limits in Claude Code return to their standard levels. There is no billing change and no plan change, but your weekly capacity quietly shrinks by a third relative to today.

That means September 1 is not a soft transition. If your team plans around an August baseline of 100%, the September baseline is effectively 67% of what you have been running, unless you adjust. Projects that comfortably fit inside the boosted weekly window this month can start brushing the standard limit within a week or two of the reset.

Plan ahead for this in three concrete ways:

• Front-load the heavy, token-hungry work into the remaining promotion window, especially anything you keep deferring because it “won’t fit in the weekly allowance.”
• Re-test your actual tolerance on a normal week. If you have been running at 90% of the boosted limit, you are likely running over the standard limit already, and September will be tight.
• Decide now whether the post-promotion level justifies a plan move or a routing change, rather than discovering it reactively once the wall hits.

Team plans and prorated realities

The extension applies to Team plans too, which is the part most finance and ops folks should note. Team plans mix a monthly per-seat price with weekly usage limits shared across the workspace. A 50% higher weekly workspace limit for the rest of August means more shared headroom for the same seat count, which is effectively free capacity on an already-budgeted spend.

The other consideration is timing. If you added seats or upgraded a plan recently, confirm the promotion is reflected on those seats. Community reports and GitHub issues have surfaced cases where a tier upgrade was not immediately reflected in weekly limits, so the displayed allowance did not match the purchased tier right away. With a deadline now visible, it is worth running /usage on the workspace and comparing against your plan tier rather than assuming the numbers are aligned.

The bottom line for your Claude Code budget

The extension is the same 50% promotion Anthropic has used since May, now locked to August 31. For heavy users it is one of the simplest ways to compress token spend this month: you get more weekly capacity at no cost, but only in Claude Code, only on eligible subscription plans, and only for weekly limits, not the 5-hour burst cap.

Use the next two weeks to run the work you have been postponing, verify your team’s displayed limits against the plan, and model your September baseline at the standard level. When the promotion ends, your weekly allowance drops by a third, and the teams that set up the transition before August 31 are the ones who do not end up paying API rates or switching plans in a panic on September 1.

Keep an eye on /usage, confirm your tier is reflected, and treat the remaining window as the free capacity it is.