Fifty index points of weekly capacity went on in May; twenty-five come off on September 14 and twenty-five stay [5][14]. That is half the promotion folded into the standard allowance and half retired [15]. The floor a team can plan on into next year therefore sits above April's, while the ceiling it has worked against since mid-May comes down [5].
Capacity planning runs off a different figure than the one in the announcement. A team that wants to hold this summer's throughput past the 14th has to replace 25 index points, and measured against the new permanent level that is a 20% top-up rather than a 17% one [16]. Anthropic has published no absolute token or prompt counts for any plan, so that fifth cannot be turned into a purchase-order line; it can only be read off a team's own consumption in the weeks either side of the change [7].
How much it hurts depends on the shape of the week. Anthropic's plan multiples describe per-session usage, while a separate weekly limit runs across models and resets at a fixed time assigned to each account, which is why a subscriber can be out of weekly capacity with a fresh five-hour session available [19]. Karl Kahn's proposed class action, filed on June 14 in the Northern District of California, alleges that one full five-hour session consumed 15% of his weekly allotment after an April upgrade [17]. Rebase that allegation onto the new cap and the same session becomes about 18% of the week, roughly 5.6 full sessions where there had been 6.7 [18]. No class has been certified, and Anthropic declined to comment [17].
A skeptic on the finance side would say a permanent 25% above the pre-May baseline is a better asset than a promotion that can lapse at any renewal date, and as a description of the trade that is correct [2]. The answer is that the two halves of it are paid by different people. Removing the expiry date is worth something to whoever signs the renewal and nothing to the engineer who committed September work against the summer ceiling, and the promotion's deadline had already been extended several times, which is what teaches a team to plan on it [14].
The paperwork has not caught up with the policy. The Help Center entry still describes the boost as running to 11:59 PM Pacific on August 31 before reverting to the standard cap, while the ClaudeDevs developer account puts the changeover at September 14 [8], and no exact switchover time or regional sequence has been given [9]. The scope question is sharper for administrators: the announcement names Claude Code weekly limits on the Pro, Max, Team and seat-based Enterprise plans [10], and says nothing about the Free and usage-based Enterprise plans the May boost excluded [13].
This week's item is a re-plan. The longer-run item is that per-seat coding capacity is metered in units no buyer can audit, which is what lets a 25% raise and a 17% cut describe the same event [7]. The five-hour session limits doubled on May 6 are untouched by any of this [12], the Reddit complaints circulating are anecdotes rather than a churn count [21], and Anthropic says it is working on changes meant to make customers feel they get more from Claude [23]. Until those arrive, the defensible September plan is the smaller number.
