QWE AI Academy Here’s the part nobody’s talking about: Anthropic just doubled the Claude Code 5-hour window, but they didn’t touch the weekly cap. So if you were already burning through your weekly bucket on Wednesdays, you’re now going to hit that wall faster – not later. The new higher usage limits for Claude are real, but they reshape when you can spend, not how much.
The whole thing dropped on day one of Anthropic’s Code with Claude conference, paired with a SpaceX compute deal involving the same Colossus 1 facility xAI built. Reactions on Hacker News and r/ClaudeAI split between “finally” and “wait, Musk owns this datacenter now?” Both can be true. Skip the news recap – here’s what changed for your actual workflow (as of May 2026).
What actually changed (the short version)
Three things flipped on the same day. Per Anthropic’s announcement:
- Claude Code’s five-hour rate limits doubled for Pro, Max, Team, and seat-based Enterprise plans
- Peak-hours throttling removed on Claude Code for Pro and Max accounts
- Opus API rate limits jumped hard – Tier 1 input limits went from 30K to 500K tokens per minute, a 1,500% increase. Output went from 8K to 80K (900% up).
The compute behind it: access to the full capacity of Colossus 1 in Memphis, Tennessee – over 300 megawatts and 220,000+ NVIDIA GPUs, rolling out within the month. The free plan is the only tier that gets nothing from this announcement.
Step 1: Check what tier you’re actually on
Before changing anything, find out what bucket you’re sitting in. The new ceilings are useless if you don’t know your starting point.
If you’re on Pro/Max (Claude Code subscription): Open your terminal and run:
/statusEasy to miss – the /status command shows your remaining allocation and which tier you’re on, all in one line. You can also hit Settings → Usage in the Claude web app for the same breakdown in a visual format.
If you’re on the API: Tier advancement is automatic. Anthropic’s rate limits documentation confirms limits are set at the organization level – you can see your org’s current ceiling on the Limits page inside the Claude Console. No form to fill out, no request to submit. The new numbers should already be live.
Step 2: Use the new Opus API limits (if you actually need them)
The headline jump is the Opus rate limits. Here’s the full table for input/output tokens per minute (ITPM/OTPM), from Anthropic’s published numbers:
| Tier | ITPM (old → new) | OTPM (old → new) |
|---|---|---|
| Tier 1 | 30K → 500K | 8K → 80K |
| Tier 2 | 450K → 2M | 90K → 200K |
| Tier 3 | – → 5M | – → 400K |
| Tier 4 | – → 10M | – → 800K |
Tier 1 only requires $5 in cumulative deposits – most paying API users qualify automatically. The deposit isn’t a fee; it sits in your account as prepaid credit. One thing worth flagging from the API docs: Claude uses a token bucket algorithm, meaning capacity replenishes continuously up to your maximum rather than resetting at fixed intervals. That matters for burst-heavy workloads – you’re not waiting for a clock to tick over.
Step 3: Rework your session strategy
Wider 5-hour pipe, same weekly tank. That combination flips the old optimization logic on its head.
Before this change, most Pro/Max users hit the per-window cap mid-session and walked away with weekly headroom they couldn’t consume. The bottleneck was the window, not the week. Now? The window is wide enough to drain your weekly budget fast if you’re not deliberate about it. Front-load the heavy reasoning work into one tight session, then shift down to Sonnet for execution. claudefa.st’s model selection analysis puts Sonnet at roughly 5x less usage-limit draw than Opus for equivalent work – move the heaviest stage off Opus and you’ve cut that stage’s consumption by ~80% without changing the output.
Practical pattern: Use Opus for planning and architectural decisions at the start of a session, then switch to Sonnet for implementation. With the doubled 5-hour window, a full plan-then-execute cycle fits in one session – something that often required two separate windows before.
Common pitfalls with the new limits
The announcement is clean. The reality has sharp edges.
- Weekly caps did NOT change. claudefa.st’s analysis flags what the announcement didn’t say: weekly caps are unchanged. Only the 5-hour rate-limit window and the peak-hour throttle moved. Your weekly bucket is the same size it was before. Power users will hit the weekly ceiling earlier in the week now, not later.
- All Claude surfaces share one bucket. Per Anthropic’s support docs: usage from claude.ai, Claude Code, and Claude Desktop all counts toward the same limit. Doubling Claude Code’s window doesn’t help if you also run heavy sessions in the web app.
- Compute is rolling out “within the month.” The limit changes were effective immediately, but Colossus 1 capacity is still coming online. 429 errors during peak demand may persist for a few weeks while the underlying infrastructure catches up.
- Tier 1 requires an actual $5 deposit. Free trial credits don’t qualify. If you’re on a free plan, this announcement doesn’t affect you.
The API tier upgrade is automatic but invisible – no email notification arrives. Check the Console Limits page directly if you’re unsure where you stand.
The stacking question
If you’re regularly hitting limits even after optimizing session strategy, the practical fix is model stacking within Claude – not switching providers. The math is already in the session strategy above: Opus for the hard thinking, Sonnet for execution, and that ratio cuts effective consumption by roughly 5x on the execution half. Most users who think they need a plan upgrade actually just need to stop running Opus on tasks Sonnet handles equally well.
The Musk angle is too funny to skip entirely. He’s publicly called Anthropic “misanthropic and evil” – and then posted on X that he was “impressed” with the team and that Claude will “probably” be good after meeting them. SpaceX’s compute is now powering the service he criticized. Money beats vibes, apparently.
Your next move
Open a terminal, run /status in Claude Code, and screenshot the output. Compare it to your usage from last week. If you were hitting the 5-hour ceiling 3+ times per week, you’ll feel the new limits immediately – but watch the weekly cap now, which most users never had to track before. Set a reminder for day 5 of your weekly window to check where you stand.
FAQ
Do I need to do anything to get the new limits?
No. They auto-applied to your account on the announcement date if you’re on a paid plan.
Why am I still getting rate-limited if the limits doubled?
Check Settings → Usage first – it tells you which cap you’re hitting, and the answer changes everything. If it’s the weekly cap, the doubled 5-hour window isn’t your problem. Fixes for a weekly cap hit: upgrade your plan, enable pay-as-you-go top-up on top of your subscription, or wait for the reset. If it’s still per-minute throttling during peak hours, the Colossus 1 compute is still rolling out – give it a few weeks.
Should I upgrade my API tier to take advantage of this?
Only if you’re actually hitting the per-minute ceiling, not the daily quota – and those are two different problems with two different fixes. The new Tier 1 numbers (500K ITPM, 80K OTPM on Opus) cover most prototyping and small-app use cases without any action on your part. The move to Tier 2 makes sense when you’re putting Claude in front of real users or running parallel agentic workflows where multiple calls fire simultaneously. The deposit threshold isn’t a fee – it’s prepaid credit – so the only cost of jumping early is the opportunity cost on that cash sitting in your account.