What happened
Claude Code, Anthropic’s coding agent, caps how much you can use it each week. Hit that cap and your sessions pause until the weekly reset. On August 29, Anthropic’s official developer account, @ClaudeDevs, announced that starting September 14, it is permanently raising those standard weekly limits by 25% for Pro, Max, Team, and seat-based Enterprise plans, meaning Enterprise contracts billed per named user rather than by usage volume.
The increase uses the original standard limit as its baseline, rather than the temporarily boosted allowance. Since earlier this year, Anthropic has run a temporary 50% boost on top of the standard limit, extending it every few weeks rather than committing to it. The most recent extension kept the boost through August 31.
Anthropic had said it hoped to make the boost permanent. Instead, on September 14, that temporary 50% boost goes away and gets replaced by a smaller, permanent 25% boost. Anthropic’s own post does the math for you: compared to what you have right now, that’s a 17% reduction in weekly limits.
To make the percentages concrete with a round, illustrative number, not Anthropic’s actual figure: if your plan’s original weekly limit was 100 units, today’s temporary boost lifted that to 150. The new permanent limit lands at 125, which is 25% above the original baseline, but 17% below the 150 you’re used to working with today.
Anthropic says it’s “working on exciting changes that will make it feel like you’re getting more from Claude, while having more visibility and control of your usage,” without giving a date or specifics.
Why it matters
The earlier announcement extended a temporary boost. The August 29 announcement set a permanent allowance that was lower than the boosted limit.
If your workflow has settled into a rhythm around the boosted limit (long agent sessions, running Claude Code across multiple projects in parallel, or leaning on the auto-continue feature that resumes sessions automatically once your limit clears) the announced reduction means less weekly headroom from September 14. That’s true even though the new permanent number is still higher than the original, pre-boost limit it replaces.
Who should care
Anyone on a Pro, Max, Team, or seat-based Enterprise plan who runs Claude Code heavily enough to notice weekly limits at all. If you rarely come close to your cap, this change won’t touch your week. If you’re already budgeting your usage to the current boosted ceiling, plan for less headroom after September 14.
What builders should do next
Type /usage to see current consumption and your weekly cap. Use that display when planning work rather than relying on the historical temporary boost.
If your weekly allowance regularly runs low, prioritize the sessions that matter most. To reduce usage, consider trimming exploratory or throwaway sessions, spreading heavy work more evenly across the week instead of running it all in one or two days, or reviewing your plan’s actual allowance against representative tasks. /usage shows the current allowance and reset time. Compare that display with the announced change rather than assuming it shows both limits.
End of article