Anthropic Doubles Claude Code's Limits: What About Your Budget?

Anthropic has just doubled Claude Code's limits, and on paper, that's good news for anyone running a dev project on an AI budget. Except the change only touches the 5-hour window, not the weekly cap that blocks most teams at the end of a sprint. On one engagement I oversee from Vietnam, my dev burned through his window twice in a single day before the announcement even landed. Here's what this change really does to your cost and your timeline, and what it leaves unsolved.

What changed with Claude Code's limits since late July 2026

On 25 July 2026, Anthropic announced three adjustments tied to a new compute deal (compute being the server capacity that runs the models) with SpaceX. First, 5-hour windows are doubled for Pro, Max, Team and seat-based Enterprise accounts. Second, peak-hours throttling (automatic rate limiting) is gone for Pro and Max. Third, API rate limits on Opus models have been raised.

I see this as turning the tap up, not enlarging the tank. The amount of work you can push through a 5-hour session has doubled, but the size of the weekly bucket is exactly what it was the day before. In practice, a dev already working flat out 8 hours a day now absorbs more work per window, but hits the weekly wall at the same rate as before.

Why did Anthropic double the windows now?

Pressure had been building for months. An Anthropic employee had publicly acknowledged working on a peak-hours fix after a wave of complaints about limits being hit in one or two prompts, even on the $200-a-month subscription. On 21 April 2026, Anthropic had even quietly tested pulling Claude Code from the $20 Pro plan to ease the load on its infrastructure, before backpedalling 48 hours later under developer pressure. The SpaceX deal solves the problem from above: more compute, so more headroom to hand out, without touching the pricing model.

The weekly cap, the real obstacle this change doesn't touch

A dev who ships fast inside a 5-hour window can still find himself stuck on Thursday if his weekly quota is spent. That's exactly what one user reported on r/ClaudeCode in late July, days after Anthropic's announcement: his perceived velocity dropped despite theoretically more generous limits, to the point of switching to Sonnet for simple tasks just to make it to the end of the week.

On one of the engagements I'm currently running, the senior dev doubled his useful working window in a single session, but still had to slow down on Thursday to avoid getting locked out on Friday. Doubling the 5-hour window changes nothing about the weekly cap, and it's that cap which decides whether your project ships on time or waits for a reset.

What does getting blocked mid-sprint actually cost?

A few hours of blockage in the middle of a working day translates directly into lost days on the timeline, especially if your dev has to wait for a window reset or fall back to a weaker model to conserve quota. According to an analysis published by Product Compass, a user paying $1,389 a month for a given workflow got that down to $200 for exactly the same volume of work, by fixing four internal causes: cache misses (losing the prompt cache, billed at up to 20 times the cost of a cached read), bloated context, the wrong model for the task, and the wrong input format. The plan was never the problem. The way it was being driven was.

What this actually changes for your budget and your timeline

On paper, $200 a month for a senior developer looks like a rounding error next to a salary or a standard day rate. The real hidden cost isn't the subscription, it's the dev time burned working around limits instead of shipping. A dev spending an hour a day tuning his prompt cache or juggling Sonnet and Opus to save quota is an hour that produces no shipped feature.

The table below compares the three Claude Code plans on the criteria that matter to a decision-maker: cost, model access, and the real risk of getting blocked mid-engagement.

Should you move to the $200 plan to avoid getting blocked?

Not automatically. The trap in the Max 20x plan sits in a detail most teams discover too late: Fable 5 has no quota of its own. On Max plans and premium Team or Enterprise seats, it draws on the same weekly allocation as every other model, capped at 50% of it, and weighs roughly twice as much as an Opus session in that calculation. That's exactly what one user on r/ClaudeCode ran into trying to generate a simple PDF guide in Ultracode mode with Fable 5: 5-hour window drained in under 30 minutes, final output delivered 6 hours later with layout defects. Moving to $200 without watching which model consumes what solves nothing, it just moves the wall.

Hiring a dev in-house versus outsourcing to a team already calibrated for these constraints

This is where the real business decision sits, and I should be upfront: I run a team of AI-augmented senior developers at Extra Dev, so I have an obvious bias here. That bias also comes from handling these quota trade-offs day to day on live engagements, not just in theory.

An in-house senior dev discovering these constraints by walking into them loses measurable time to trial and error. On the engagements I oversee, the rule is simple: lock your tools down at the start of the session (adding or removing a tool mid-session invalidates the prompt cache and forces a full, expensive re-read), choose the model based on the actual difficulty of the task rather than out of habit, and break large chunks of work into short, testable tasks so you never depend on a single 5-hour session. That's an operational skill in its own right, not a configuration detail.

"The real edge isn't using Claude Code, it's building a disciplined production system around its limits, otherwise the generated code quickly becomes unmanageable."

Vincent, August 2026

I went into this at greater length in our analysis of the latest Claude Code update and its budget impact, and the plan-by-plan comparison by developer profile is available in our Claude Code pricing guide. The GoLive Software blog also covers these time-and-materials versus fixed-price trade-offs on the staffing side, for anyone who wants to dig into the budget mechanics beyond the tool itself.

The decision criterion that actually matters

The market for AI-assisted development tools keeps growing fast: according to Gartner, AI coding assistants rank among the fastest-adopted software categories in enterprise over the 2025-2027 period, which explains the strain on Anthropic's infrastructure and the need for these capacity adjustments. It's no accident that the limits move so often: demand is growing faster than providers can comfortably absorb.

For your project, the criterion isn't "which plan" but "who manages quota optimisation". If you hire an in-house dev who learns these settings on the job, budget several weeks of lost velocity before he masters caching, task breakdown and model selection. If you hand the work to a team already drilled on these constraints, the cost of blockage disappears from the first sprint.