Claude Code weekly limits fell 16.7%. Here's why

Claude Code’s weekly allowance is getting smaller for plans covered by Anthropic’s promotion. From 14 September 2026, the bonus falls from 50% to 25% above the original allowance. That means 16.7% less weekly capacity than during the promotion. Anthropic says the promotion did not affect five-hour limits. [1]

Why did Claude Code’s weekly limits change?

Anthropic’s temporary weekly boost ended, and a smaller permanent increase replaced it. The help page says the promotion ran from 13 May through 13 September 2026, ending at 11:59 p.m. Pacific Time. From 14 September, eligible plans retain a weekly allowance 25% above the level before the promotion. [1]

The confusing part is the reference point. Both the old 50% bonus and the new 25% bonus are measured against the allowance before the offer began. If you compare those two percentages directly, it is easy to call this a 25% cut. That is not what the arithmetic says.

I would describe it as a partial rollback of the promotion. Someone comparing September with the original allowance still has more capacity. Someone who built a working routine around the promotional allowance has less. Those statements describe the same policy from different starting points, which is why the distinction matters more than the wording of the bonus.

A post in Reddit’s r/ClaudeCode on 14 September reacted to the smaller limits and linked Anthropic’s promotion page. The reaction makes sense if the promotional allowance is the capacity you had been relying on. It does not, by itself, establish that Anthropic changed how individual tasks are metered. [2]

Is this a 25% cut or a 16.7% cut?

Compared with the promotional allowance, the reduction is approximately 16.7%. Set the original allowance to 100 units. The promotion made it 150, and the replacement makes it 125. Losing 25 out of 150 units means losing one sixth of the capacity you had during the offer.

The new allowance is five sixths of the promotional allowance. This table is a way to compare the policy, not a conversion into a guaranteed number of prompts. Anthropic’s general limits documentation says consumption depends on factors including conversation length, task complexity, model choice and features used. Two sessions can therefore consume different amounts even when they contain the same number of messages. [3]

For planning, the useful comparison is with work you already understand. If a particular workload regularly came close to the promotional weekly limit, a smaller allowance leaves less room for that same workload, assuming its consumption stays the same. That does not establish how many hours of coding you will lose. It tells you which routines are worth checking before you rely on them for a deadline.

I would avoid converting the change into a claim such as “Max now gives you X tasks per week.” The published percentages support a relative comparison. They do not supply a fixed task budget.

Which plans and limits does the change affect?

The offer covered Pro, Max, Team and legacy seat-based Enterprise plans. Anthropic excludes Free and consumption-based Enterprise plans from that promotion, so the same percentage calculation should not be applied to every Claude account. The offer was automatic for eligible plans. [1]

The distinction between a weekly allowance and a five-hour limit also matters. The promotion concerned the weekly allowance; Anthropic explicitly says five-hour limits were not affected. A user who stops because the shorter window is exhausted is facing a different restriction from a user who exhausts the weekly allowance. [1]

For Pro and Max users signed in through their subscription, Anthropic says Claude and Claude Code share usage limits. Moving from the terminal to another Claude interface does not create a separate subscription allowance. API-key authentication is a different billing route, so check how the session is authenticated before combining its usage with the plan’s quota. [5]

For a team, I would explain the change in terms of the actual plan and the actual window. “Our weekly promotional allowance is lower” is useful. “Claude has cut all its limits” is too broad to guide anybody’s next step.

Why doesn’t this explain every Reddit complaint?

Some complaints predate the policy change, so the end of the promotion cannot explain them. On 13 September, an r/ClaudeCode user reported hitting the weekly limit unusually quickly on a Max plan. The thread was posted before the stated end of the promotion. It documents a user’s experience, not a confirmed metering defect. [4]

That chronology is important because two different questions can otherwise get merged. One asks why the advertised weekly allowance is smaller after the deadline. Anthropic’s promotion page answers it. The other asks why a particular account consumed its allowance unexpectedly fast before the deadline. Answering that requires details of the account and workload that the percentage change does not provide.

The general usage documentation supplies possible factors to inspect, such as model choice and conversation complexity, but it does not diagnose that Reddit user’s session. I found no official confirmation tying the cited incident to an accounting bug. Treating the complaint as proof of one would turn a reasonable troubleshooting question into an unsupported claim.

What should you check before buying more capacity?

First identify the allowance involved, then compare similar work on either side of the change. I would record the plan, model, effort setting, approximate conversation size and the limit message, along with the relevant reset time. Those details make a support request more useful than a screenshot of a percentage without context.

For a recurring task, keep the instructions and input comparable while you observe the next run. Changing models, adding parallel agents and starting a much larger conversation at the same time makes it harder to tell whether the new weekly allowance is the reason work stopped earlier. This is a troubleshooting approach, not a benchmark I have run.

My practical reading of the announcement is straightforward: retain the larger increase as the comparison point if that is the capacity you have actually been using, and plan around the smaller allowance from 14 September. If your problem is a five-hour warning or an incident before the deadline, take that specific problem to support instead of assuming the promotion explains it.