Claude Code's temporary 50% boost expires: what the permanent replacement actually means for your weekly limit
Anthropic's permanent 25% limit increase from 14 September 2026 is a 17% cut versus the temporary boost users have relied on since May.
Anthropic’s announcement of a permanent 25% increase to Claude Code weekly limits, effective 14 September 2026, sounds straightforwardly good. It is not, quite. The detail buried beneath that headline is that a temporary 50% boost, which had been quietly extended since May 2026, expired on 13 September. The permanent replacement leaves Pro, Max, Team, and seat-based Enterprise subscribers with 17% fewer weekly tokens than they had the day before.
That gap is worth understanding clearly before you calibrate your workflows around the new numbers.
The maths behind the headline
The framing is accurate but incomplete. Put it in simple numbers: if your original baseline weekly allowance was 100 units, the temporary summer boost took you to 150. The permanent increase takes you to 125. Compared with the original baseline, yes, that is a 25% gain. Compared with what you have been working with since May, it is a reduction.
Anthropic initially emphasised the first comparison in its announcement. After a pointed community reaction, the company pulled that post and published a revised version that explicitly acknowledges the net reduction. Credit where it is due for correcting the messaging, but the fact that the correction was needed says something about how the change was initially framed.
What has actually changed since May
To understand the September shift, it helps to know the full sequence.
On 6 May 2026, Anthropic doubled the five-hour rolling session limit across all paid plans and removed peak-hour throttling for Pro and Max users. Weekly limits were untouched at that point.
A week later, Anthropic layered on a separate temporary 50% increase to weekly caps. The company was clear this was a promotion tied to capacity, not a policy change. What followed was a series of extensions: the boost was renewed through mid-July, then July 19, then August 19, then August 31, and finally through September 13. Each extension kept the 50% in place long enough that many users stopped thinking of it as temporary.
From 14 September 2026, the new permanent baseline is 125% of the original, the temporary boost is gone, and the doubled five-hour session limits from May remain in place. Only the weekly cap has moved, and only downward relative to the promo peak.
What is exempt from the cap
One genuinely useful change arrived alongside the limit adjustment. Auto mode’s permission classifier, the background process that decides whether Claude Code can take an action without stopping to ask you, no longer counts its calls against your weekly allowance on Pro, Max, and Team plans.
This matters because auto mode became the default permission mode for new Claude Code sessions on those plans on 14 August 2026. Before the exemption, every classifier call was quietly drawing from the same weekly pool as your actual work. Removing that hidden overhead is a real, if modest, improvement. Note that Enterprise plans are not yet covered by this exemption; on Enterprise surfaces, classifier calls still count toward token usage.
What this means for your workflow
If you use Claude Code casually and rarely approach your weekly limit, the September change will not affect you noticeably. The permanent 25% increase over the original baseline is a genuine, if modest, improvement over where things stood before May.
If you are a heavy user who calibrated your workflow around the 50% boost, the adjustment requires attention. A practical rule of thumb: if your weekly usage bar in Settings regularly exceeded 67% of the displayed limit during the summer, you will hit the cap under the new permanent figures.
For engineering teams running automated Claude Code pipelines, the change is worth auditing before 14 September. Pipelines built around the boosted capacity are now over-provisioned relative to what the plan actually delivers. Every prompt, tool call, file read, and thinking block draws from the same shared weekly pool, and Claude Code, Claude chat, and Cowork all pull from the same allowance.
You can check your actual limit at any time by running /usage in the Claude Code CLI. If you hit the cap and need to keep working, Anthropic allows you to purchase usage credits at API rates. Team and seat-based Enterprise members can continue working without interruption once credits are added rather than hitting a hard block.
The broader pattern
Anthropic’s rationale across multiple statements has been consistent: serving agentic coding workflows at scale is expensive, and the summer’s 50% was always intended as temporary capacity relief, not a new standard. The permanent 25% increase is framed as locking in part of that expansion.
That is a fair explanation, but it sits awkwardly against the background of the Claude Max usage-limits dispute, in which subscribers have contested whether marketed multipliers match delivered capacity. A permanent “increase” that reads as a reduction compared with the previous four months is exactly the kind of framing gap that keeps that scepticism alive.
The /limit-reset command, which resets your session limit once per week, remains available, though the weekly cap itself applies regardless.
The short version
The 50% temporary boost expired 13 September 2026. The permanent replacement is 25% above the original baseline, which is 17% below where heavy users have been working. The five-hour session limits from May are staying. Auto mode classifier calls are now free on Pro, Max, and Team. If your usage regularly ran high during the summer, check your numbers and plan accordingly.