If you’ve been running Claude Code hard the last few months, tonight is the night your headroom shrinks back down.

At 11:59 PM PT, Anthropic’s temporary 50% bump to Claude Code’s weekly usage limits runs out. It’s the fourth deadline Anthropic has set for this promotion since introducing it in May, and this time there’s no indication another extension is coming. Same subscription, same price, less capacity. For teams that built sprint plans, CI pipelines, or just daily habits around that extra room, the math changes today.

Mike Vizard, editor-in-chief of DevOps.com, asked a fair question when this story crossed his desk: Is this new? The honest answer is no and yes. Weekly caps on Claude Code aren’t new at all — Anthropic put them in place back in July 2025, with an effective date of August 28 that year, after what the company described as “unprecedented demand” for the tool. Some subscribers were running Claude Code continuously, 24 hours a day. Others were sharing or reselling access in violation of the terms of service. Anthropic said the caps would affect fewer than 5% of subscribers based on usage patterns at the time, and it built in separate weekly allowances for Sonnet and Opus, depending on the plan tier.

The original 2025 caps were tiered by plan. Pro subscribers at $20 a month got roughly 40 to 80 hours of Sonnet 4 usage per week. Max, at $100 a month, got 140 to 280 hours of Sonnet, plus 15 to 35 hours of Opus. Max, at $200 a month, got 240 to 480 hours of Sonnet, plus 24 to 40 hours of Opus. Anthropic was upfront that actual usage would vary depending on codebase size and task complexity, which is really just another way of saying the caps were estimates, not hard science.

What’s new is everything that’s happened since. In May 2026, Anthropic doubled the five-hour rolling session limit across all paid plans and dropped peak-hour throttling for Pro and Max users, so performance no longer dipped during high-traffic windows. Weekly limits didn’t move in that update. Then, a week later, Anthropic layered on a separate, temporary 50% increase to those weekly caps — a promotion, not a permanent policy change. That promotion has been extended three times since: from an original mid-July cutoff to July 19, then again to today, August 19. Each extension came through a support-center update or a post on X rather than a formal announcement, which is its own small signal about how Anthropic is managing this.

There’s a second thread tangled into this one. Anthropic’s newer coding model, Fable 5, was originally scheduled to be removed from the subscription tiers entirely on July 19. Instead, it became a permanent option on the Max and Team Premium plans, drawing up to half of a user’s weekly limit from the same shared usage pool as everything else. Pro and Team Standard subscribers didn’t get the same deal. They lost access to Fable 5, got a one-time $100 credit, and now pay per token to keep using it. That’s a meaningfully different cost structure for anyone doing sustained, model-heavy work.

Put those pieces together, and the pattern is clear enough. Anthropic has spent the past year and a half tightening, loosening, and re-tightening the knobs on Claude Code access — rolling caps out, doubling session windows, offering a discount, extending it three times, and now letting it lapse. None of it changes the subscription price. It changes how much work you can actually get done inside it.

Mitch Ashley, VP and practice lead for software lifecycle engineering and AI-native software engineering at The Futurum Group, has pointed to the structural issue underneath moves like this one. Commenting on a related Anthropic pricing reversal earlier this year, he said the underlying tension doesn’t go away just because a company backs off a specific change: “Subscription pricing was built for human-paced usage, and automated agents consume tokens at a scale model providers cannot subsidize indefinitely.” That’s the story here too. A flat monthly fee assumes a human is typing, thinking, and taking breaks. An AI coding agent running against a CI pipeline or working through a large migration doesn’t pause. Something has to give, and lately it’s been the ceiling on how much of that work a subscription actually covers.

For DevOps teams, the practical response isn’t complicated, even if it’s a little tedious. Treat Claude Code capacity like any other finite compute resource: track weekly consumption the way you’d track a cloud spend budget, front-load the token-heavy work while there’s still headroom, and have a fallback model or tool ready for the days you hit a wall. Anthropic has shown it will adjust these limits again — it’s done so five times in the past 15 months — but each adjustment has favored the company’s cost structure over the subscriber’s planning certainty.

Tonight’s change is small on its own. But it’s one more data point in a longer trend: as coding agents get better at working around the clock, the pricing models built for people will keep getting stress-tested. Expect more of these adjustments before the industry settles on something durable.