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.
Read that as an increase and you’d be wrong about what changes for you tomorrow. 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. We covered the most recent extension on August 19, when Anthropic pushed the deadline to August 31 and said it hoped to make the boost permanent. It didn’t. 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
This is the second time in two weeks that Anthropic has moved the goalposts on Claude Code capacity, and the direction just reversed. The August 19 news was about the boost sticking around a little longer. This is Anthropic finally making a permanent decision, and that decision gives you less room than you have this week.
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) you’ll hit the wall sooner starting 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 inside Claude Code now to see your current consumption and where it sits relative to your weekly cap. That gives you a real baseline before the drop, rather than guessing at how close you actually run to the limit.
If you’re consistently using most of your current boosted allowance, use the two weeks before September 14 to figure out which sessions matter most. Options worth weighing before the cutover: trimming exploratory or throwaway sessions, spreading heavy work more evenly across the week instead of running it all in one or two days, or checking whether a Team or Enterprise seat changes your math if you’re currently on Pro or Max. None of that is guesswork, since /usage will tell you exactly how much room you have left under either number.
Anthropic has changed this boost’s expiration date multiple times this year without locking it in. This time it did lock something in, just not the number most users were hoping for. Treat September 14 as a real deadline, not another one that might slip.
End of article