At 11:59 PM PT on August 19, Anthropic's temporary promotion for Claude Code usage limits expires. The tool reverts to the weekly caps originally introduced in July 2025 after a series of extensions that have now concluded without further indication.
The Architecture Shift
For teams relying on automated agents, this expiration represents a structural change rather than just a minor adjustment. The underlying tension driving these policy shifts is the mismatch between flat subscription pricing and infinite compute consumption by AI coding agents running against CI pipelines or handling large migrations.
Tiered Capacity Constraints
The current baseline limits are estimates, not hard science, but they function as finite resources that must be tracked. The tiers remain:- Pro ($20/mo): Roughly 40 to 80 hours of Sonnet 4 usage per week.
- Max ($100/mo): Up to 15-35 hours of Opus and significantly higher limits for Sonnet (up to 280 hours).
- Team Premium: Access includes the newer Fable 5 model, which draws up to half a user's weekly limit from the shared pool.
Note that Pro and Team Standard subscribers lost access to Fable 5 entirely during this period. They received a one-time credit but must now pay per token for sustained use of that specific capability if they require it, altering their cost structure significantly compared to Max or Premium tiers.
Operational Implications
The expiration signals the end of an era where capacity was treated as effectively infinite. Teams building sprint plans around these tools must now treat Claude Code consumption like any other cloud spend budget:
- Track weekly consumption strictly.
- Front-load token-heavy work while headroom remains available before the cap resets or hits a wall.
- Maintain fallback models ready for days when usage limits are exhausted, as agents will not pause automatically during high-traffic windows in the same way human users might expect.
This approach requires shifting from reactive monitoring to proactive capacity planning. The company has adjusted these knobs five times over 15 months—rolling caps out and tightening them again—but each adjustment favors cost structure stability over subscriber certainty.
What This Means For Practitioners
The industry is moving toward pricing models that better reflect the scale of automated agent workloads. Until a durable model emerges, practitioners should expect further adjustments to these limits before they settle on something stable for long-term architecture planning.
