Anthropic Boosted Claude Code Weekly Limits by 50 Percent Through July 13

Anthropic just pushed a 50% increase to Claude Code weekly usage limits, and it's already applied to your account. No opt-in, no settings toggle. If you're on Pro, Max, Team, or a seat-based Enterprise plan, you have more headroom starting right now.

The promotion runs through July 13 at 6PM PDT / 1AM GMT. It covers every surface where Claude Code runs: the CLI, IDE extensions, the desktop app, and the web interface. And it stacks on top of the 2x increase to 5-hour limits that Anthropic announced just last week.

That combination matters. You're not just getting more total capacity for the week. You're also getting a wider pipe per session. For developers running long agentic coding tasks, both constraints have historically been friction points.

What Changed and What Didn't

Claude Code operates on two distinct limit layers. The first is a rolling 5-hour window that governs how much you can push through in a single session. This window governs burst usage, capping how many requests a user can submit within a given time frame. The counter begins from the first prompt in a session. If a developer starts at 10 a.m., the next reset occurs at 3 p.m., regardless of how many requests were made in between.

The second layer is the weekly cap. That's the absolute ceiling on total compute consumption across a rolling seven-day period. Anthropic defines an active hour not as wall-clock time, but as periods when Claude models are actively processing tokens or executing code-related reasoning. Idle moments such as file browsing or conversational pauses do not count toward this quota.

The current promotion increases that second layer by 50%. The 5-hour window itself was already doubled in the prior announcement. On May 6, 2026, Anthropic permanently doubled Claude Code's 5-hour limits for Pro, Max, Team, and seat-based Enterprise plans. Weekly caps did not change in that announcement — only 5-hour windows. So the 50% weekly boost is additive and distinct from what already shipped.

Who Gets It and Where

The increase applies to all paid Claude Code users:

• Pro ($20/month)
• Max ($100/month and $200/month tiers)
• Team (per-seat pricing)
• Enterprise (seat-based plans)

It works across every interface:

• CLI (claude in your terminal)
• IDE extensions (VS Code, JetBrains, etc.)
• Claude desktop app
• Claude.ai web interface

That applies to Pro, Max, Team, and seat-based Enterprise plans, the company confirmed. Free plan users are not included in this promotion.

How the Stacking Works in Practice

The two recent changes serve different bottlenecks, and understanding the difference helps you plan your work sessions.

The amount of work you can push through Claude Code in a single 5-hour window just doubled. The part most people will misread: the weekly caps did not change in the prior announcement. That announcement only touched the 5-hour rate-limit window and the peak-hour throttle. The current 50% weekly bump now addresses the other side of that equation.

In concrete terms: if you were previously hitting the weekly ceiling before hitting a per-session limit, the new promotion gives you meaningful additional runway. Most users were being clipped inside individual work sessions by the per-window throttle and the peak-hour cut, walking away from a session with weekly headroom they couldn't actually consume during the hours they were at the keyboard. What the combined announcements do, in effect, is unblock your weekly cap during the hours you actually want to use it.

One thing to watch: model choice still determines how fast you burn through either limit. Run Opus on every step of every task and you'll burn through the doubled per-window cap as fast as you used to burn through the old one, then crash into the weekly cap days earlier in the week. Routing Sonnet for mid-task work and reserving Opus for planning and review steps is the practical way to stretch the new headroom.

The Infrastructure Behind the Increase

Anthropic's ability to expand limits is directly tied to compute capacity. The recent limit increases come as a result of Anthropic striking a deal with SpaceX for additional compute capacity. "All" of the compute capacity from SpaceX's Colossus 1 data center — 300 megawatts in the form of over 220,000 NVIDIA GPUs — will directly improve capacity for Claude Pro and Claude Max.

That compute deal is the underlying reason Anthropic can now offer both a permanent 5-hour doubling and a temporary weekly boost simultaneously. Anthropic gets the entire capacity of SpaceX's Colossus 1 data center in Memphis: more than 300 megawatts and over 220,000 NVIDIA GPUs, coming online within the month.

Anthropic is also removing its peak hours limit reduction on Claude Code, allowing Pro and Max users to operate the same across peak and off-peak times. That change was part of the May 6 announcement and remains permanent.

Key Technical Highlights

• 50% increase to weekly Claude Code limits, live now
• Stacks with the 2x permanent increase to 5-hour session limits (announced May 6)
• Expires July 13 at 6PM PDT / 1AM GMT
• No action required — applied automatically to all eligible accounts
• Applies everywhere: CLI, IDE extensions, desktop app, and web
• Peak-hour throttling on Claude Code removed for Pro and Max (permanent change)
• Tier 1 API users are also seeing a 1,500% increase in maximum input tokens per minute, and a 900% increase to maximum output tokens per minute, with major boosts for other tiers as well

What This Means for Developers

Claude Code is an agentic coding assistant capable of reading code, editing files, performing tests, and pushing GitHub commits. It quickly became popular among developers for its ability to handle extended coding sessions and complex development tasks.

For developers running multi-step agentic tasks — think full feature branches, automated test generation, or large refactors — the compounded effect of both limit increases is meaningful. Doubled 5-hour limits help long agentic runs the most. If your workflow is "open Claude Code, hand it a feature, walk away for an hour," the 5-hour ceiling was the cap that hit you first. Doubling it pushes that ceiling out far enough that most single-feature runs do not bump into it at all.

The weekly boost then gives you more of those sessions per week before hitting a hard stop. For teams on seat-based Enterprise plans, that translates directly to fewer interruptions and more consistent throughput across the workweek.

If you're a Max plan user who needs even more capacity, extra usage allows individuals subscribed to paid Claude plans to continue using Claude after reaching their included usage limits. Instead of being blocked when you hit your session limits, you can switch to consumption-based pricing at standard API rates and continue your work without interruption.

Final Thoughts

The 50% weekly boost is a time-limited promotion, but the context around it matters. Anthropic has been threading a difficult needle: demand for Claude Code has outpaced infrastructure, and the company spent months tightening limits before it had enough compute to start loosening them. The SpaceX/Colossus deal changes that calculus significantly.

What I'd watch is whether Anthropic makes a portion of this weekly increase permanent once the July 13 deadline passes. The 5-hour doubling became permanent. If usage data from this promotion shows that the higher weekly limit doesn't destabilize service quality, there's a reasonable case for keeping some of it. The temporary framing gives Anthropic flexibility, but developers tend to build workflows around whatever headroom they have.

For now, the practical advice is simple: use it. If you've been rationing Claude Code sessions or batching tasks to stay within weekly limits, this window gives you room to work more naturally. What do you think? Are the current limits enough for your workflow, or are you still hitting ceilings? Drop your thoughts in the comments.

---