Claude Code's weekly limits rise 25% and fall 17% on the same day — both numbers are real

On August 29, 2026, Anthropic’s ClaudeDevs account posted that from September 14 it is permanently raising standard weekly limits in Claude Code by 25% for Pro, Max, Team and seat-based Enterprise plans, and that until then the current 50% increase stays in place.

Within hours the same announcement was being reported two ways: a 25% increase, and a 17% cut. Anthropic itself published the second number in a follow-up, stating that compared to today this works out to a 17% reduction in weekly limits on Claude Code.

Nobody is spinning here. It’s one announcement with two correct readings, and the arithmetic takes about thirty seconds to settle.

The 30-second version

• September 14, 2026: the published standard weekly limit goes up 25%, permanently. The 50% temporary boost ends the same day.
• The math: you go from 150% of standard to 125% of standard. That’s 83.3% of what you have now — a 16.7% reduction, which Anthropic rounds to 17%.
• Which headline is yours depends on when you started. Before May 13, it’s a raise over what you bought. After May 13, you have never seen the standard limit, so it’s a cut and nothing else.
• Not affected: the rolling 5-hour session window. The boost never covered it, and the separate May 6 doubling of session limits isn’t being reversed.
• Do this before the 14th: check /usage, take the share of your weekly cap you normally burn, multiply by 1.2. Over 100% means you’d hit the wall.

Why there are two headlines

Read the middle row as your starting point and the last row is a cut of 16.7%. Read the top row as your starting point and the last row is a raise of 25%. Both comparisons are arithmetic, not opinion.

The reason the second reading dominates the conversation is that almost nobody has been living on the top row. The boost started on May 13, 2026, originally due to end July 13. It was pushed back through the summer — publicly noted end dates of July 19, August 19 and August 31, with reporting counting four extensions in total — and now runs to September 13.

That’s four months. /usage has been showing people the boosted number that entire time. Capacity plans, tool choices, and “can our team live on Max 5×” decisions were all made against it.

Which number is actually yours

This is the part the coverage flattens, and it’s the only part that changes what you should do.

If you started paying before May 13, 2026: you bought a plan at the standard limit, got a temporary 50% on top for four months, and from September 14 you keep a permanent 25%. Against what you agreed to buy, you’re ahead. The boost was labelled temporary and it behaved that way, just slowly.

If you started after May 13, 2026: you have never once run Claude Code at the standard weekly limit. Every capacity intuition you have was formed on the boosted number. For you the September 14 change is a 17% cut, full stop, and it will be the first limit change you’ve experienced. Three and a half months of new Claude Code customers are in this group.

Neither camp is confused. They’re describing different experiences of the same product accurately, which is why the argument doesn’t resolve.

The structural lesson is worth stating plainly, and it isn’t specific to Anthropic: a temporary allowance extended four times across four months stops being a promotion and starts being the product, at least in the way people plan around it. The number in your terminal is a current state, not a commitment. That’s a fair thing for a vendor to do under capacity pressure — Anthropic has cited platform stability as the reason — and it’s also a fair thing for a team to notice when it decides how much of its workflow to hang on one meter.

Credit where it’s due: Anthropic published the 17% figure itself rather than leaving readers to derive it. A company optimising purely for the headline doesn’t do that.

What doesn’t change

Conflating the two Claude Code limits is the most common mistake in this whole topic, and this announcement is a good moment to keep them apart.

The 50% boost only ever applied to the weekly caps. Separately, on May 6, 2026 Anthropic doubled the five-hour rate limits for the same plans and removed the peak-hours reduction — that change is not being reversed. So if your pain is running out at 3pm and getting it back at 8pm, nothing in this announcement touches you.

Anthropic also said it’s working on changes that give users more visibility and control over their usage. That’s unshipped, so it’s a note for the calendar rather than something to plan against.

The calculation to run before September 14

Cheap, takes a minute, and it’s the difference between adjusting now and discovering the wall mid-sprint.

1. Run /usage in Claude Code and note the share of your weekly cap you typically reach — not the 5-hour one.
2. Multiply it by 1.2. (You’re converting today’s 150% baseline to the new 125% one: 150 ÷ 125 = 1.2.)
3. If the result crosses 100%, you’d hit the weekly wall under the new limits.

If you land over, the cheap fixes come before the expensive one. Move routine turns to Sonnet and keep Opus for the problems that need it — model choice swings burn rate harder than almost anything else. Trim what loads into every session, since instruction files are a recurring per-session tax. Then, if you’re still over, price the overflow: Usage credits bill at API rates, and at some volumes a tier change is cheaper than credits.

If you land comfortably under — most individual users will — this is a calendar note, not a problem.

What would change this page

Anthropic has extended this boost four times already. A fifth extension, or a change to the September 14 date, would move the numbers here; the arithmetic wouldn’t change, only which row you’re standing on. The promised usage-visibility changes are the other thing to watch, because better in-product reporting is what would make this whole calculation unnecessary.

Companion reading

• Claude Code usage limits, explained — the 5-hour window, the weekly caps, per-plan multipliers, and how to see your burn.
• Codex vs Claude Code usage limits — why the same-shaped quota empties faster on one side.
• Claude Code pricing in 2026 — when a tier change beats buying overflow credits.
• Five habits in your CLAUDE.md that are quietly burning tokens — the per-session tax you control.

Sources

1. ClaudeDevs on X — the September 14 announcement
2. Anthropic is cutting Claude Code’s current weekly limits by 17% — BleepingComputer
3. Anthropic announces a 25% increase to Claude Code limits, but there’s a 17% catch — Notebookcheck
4. Anthropic raises Claude Code weekly limits by 25% for paid plans — The Mac Observer
5. Anthropic extends Claude Code 50% weekly limit to Aug 31 — Mike Gingerich
6. Higher limits for Claude Code — Anthropic (May 6, 2026)

FAQ

Is Anthropic raising or cutting Claude Code’s weekly limits? Both, depending on the baseline. On September 14, 2026 the published standard weekly limit rises 25% permanently for Pro, Max, Team and seat-based Enterprise plans, and the 50% temporary boost that has run since May 13 ends the same day. Against the standard limit your plan nominally buys, that’s a 25% increase. Against what you’ve actually had for four months, it’s a drop from 150% of standard to 125% — 16.7% less, which Anthropic’s own follow-up rounds to 17%.

What exactly did Anthropic say? On August 29, 2026 the ClaudeDevs account posted that starting September 14 the company is permanently raising standard weekly limits by 25% for Pro, Max, Team and seat-based Enterprise plans, and that until then the current 50% increase stays in place. A follow-up the same day said that compared to today this works out to a 17% reduction. Anthropic also said it’s working on changes giving users more visibility and control over usage.

Does this affect the 5-hour session limit? No. The 50% boost only ever applied to the weekly caps. The separate May 6, 2026 change that doubled the five-hour rate limits — and removed the peak-hours reduction for Pro and Max — is a different change and isn’t being reversed. If your wall arrives mid-afternoon rather than mid-week, nothing here touches you.

How long has the 50% boost been running? Since May 13, 2026, originally through July 13. It was extended repeatedly across the summer, with publicly noted end dates of July 19, August 19 and August 31, and reporting counting four extensions in total; it now runs to September 13. Four months — long enough that anyone who started after mid-May has never seen the standard weekly limit.

What should I do before September 14? Run /usage now, while the boost is still on, and note the share of your weekly cap you typically reach. Multiply by 1.2. If it crosses 100%, you’d hit the wall under the new limits — so change something now rather than mid-sprint: routine turns on Sonnet, a lighter per-session context, or planned Usage credits overflow.

Which plans does it apply to? Pro, Max, Team and seat-based Enterprise. The free plan was never part of the 50% boost, and the change is to weekly limits only.