Jonathon's AI Wiki

Anthropic + SpaceX Compute Deal — Rate Limits Doubled (May 2026)

6 min read

Source: raw/Claude_Just_Solved_Session_Limits.md (Nate Herk YouTube walkthrough, 2026-05-07), corroborated by raw/reddit-1t5hs98.md (r/ClaudeCode “Doubled Rate Limits for Claude Code,” 1183 score), raw/reddit-1t67z6s.md (r/Anthropic Colossus 1 details), raw/reddit-1t6gsec.md (Dario Amodei “80-fold growth” quote)

At the May 7, 2026 Code with Claude conference in San Francisco, Anthropic announced a SpaceX compute partnership and three immediate user-facing changes: Claude Code 5-hour session limits doubled across Pro/Max/Team, peak-hours throttling removed for Pro/Max, and significant API rate-limit increases for Opus across all tiers. The announcement is the public resolution of months of compute-shortage pain — outages, weekly usage nerfing, the brief experiment locking new Pro subscribers out of Claude Code.

Key Takeaways

  • Claude Code 5-hour limits doubled across Pro, Max, and Team. Same plan, twice the session length. Effective immediately, no opt-in.
  • Peak-hours throttling removed for Pro/Max. The weekday-morning session-limit reduction (rolled out ~April 2026) is gone. Cloud Code usage is now uniform across the day.
  • API rate limits raised significantly for Opus models. Tier 1 input went from 30k tpm to ~500k tpm (roughly 16×); output from 8k tpm to 80k tpm (10×). All tiers got proportional jumps. Previously, only ~22 pages of context per minute were possible per tier — now ~370 pages.
  • Funded by the Colossus 1 SpaceX deal. Anthropic gets 300+ MW capacity and 220,000+ Nvidia GPUs running Claude inference at xAI’s Colossus 1 cluster. The infrastructure was provisioned fast; community signal-boosters note the irony of Musk’s earlier “Claude is misanthropic and evil” framing being followed by the partnership three months later.
  • Forward-looking: orbital compute. The bottom of the announcement notes Anthropic + SpaceX “have expressed interest in partnering to develop multiple gigawatts of orbital AI compute capacity.” Nothing this year. Framed as a long-term hedge against terrestrial-compute ceilings (power, water, cooling, community pushback).
  • Part of a broader buying spree. Existing partnerships with Amazon, Google + Broadcom, Microsoft + Nvidia, Fluid Stack. The day before the conference, Anthropic announced a Goldman Sachs JV + Blackstone partnership skewing enterprise.
  • Dario Amodei’s framing: “80-fold growth in Q1 on an annualized basis” explains the compute shortage. They planned for 10× growth; got 8× more than that. Growth this extreme makes provisioning genuinely hard — overprovisioning wastes capital, underprovisioning produces the outages users have been hitting.
  • Side-effect hypothesis (per Nate Herk): the OpenClaw/Hermes Agent terms-of-service crackdown correlates with this period. Banning subscription-pooled API access through agentic harnesses likely had both compliance and capacity-management motivations.

What this changes for builders

Five concrete shifts the source video calls out:

  1. Retest workflows that broke before on rate limits. Opus agents you abandoned 3-6 months ago because of throughput walls — try them again. The wall might be gone.
  2. Lift effort routing. If you’ve been delegating heavily to Haiku/Sonnet to stretch Pro session limits, you can now spend more on Opus without burning out the budget. Context-management discipline still matters; the budget is just bigger.
  3. The 1M context window is finally usable in production. Previously rate-limited out of practical use; the new tier-1 input ceiling makes 1M context viable for real workloads.
  4. Claude Code can sit behind production infrastructure, not just prototypes. Routines + Claude Code in the agentic loop no longer fight against your day-to-day knowledge work for session-limit budget.
  5. Multi-agent workflows are way more viable. Five sub-agents each reading 50k tokens used to be unrealistic; it now fits inside the new ceilings.

Try It

  1. Run /usage in Claude Code to see your current 5-hour session window after the upgrade. Compare the percent-used delta against a comparable session from April.
  2. Re-attempt an Opus agent build you abandoned to rate limits. Pick a multi-agent workflow you parked. Profile token throughput; compare against where you hit the wall before.
  3. Promote a Routine that was throttled. If you have a routine that was running on a strict cadence to stay under peak-hours throttling, move it to a more aggressive schedule and watch the session usage. Pro/Max should no longer hit the peak-hour reduction.
  4. For API users on Opus: request a tier review. Tier limits jumped, but Anthropic’s account-level adjustment may need a manual bump for accounts that were already throttled. Check /anthropic console → rate limits.
  5. Long-context production test. Push a real workload through the 1M-context Opus path. The previous practical ceiling around 30k tpm input made this synthetic; the new ~500k tpm tier-1 makes it real.

Reddit corroboration + community context

  • r/ClaudeCode “Doubled Rate Limits” (1183 score, 452 comments, 2026-05-06) carried the official @claudeai post in the thread root: “We’ve agreed to a partnership with @SpaceX that will substantially increase our compute capacity.”
  • r/Anthropic Colossus 1 thread (228 score, 2026-05-07) frames the political subtext: “Anthropic just got 220,000 GPUs from the man who called Claude ‘misanthropic and evil’ three months ago.” Confirms 300+ MW capacity, immediate Claude Code limit-doubling, peak-hour caps removed, Opus API rates up.
  • r/ClaudeAI Dario Amodei 80-fold growth thread (335 score, 2026-05-07) carries the conference quote explaining the shortage: planned for 10× annualized, got ~80×.
  • r/ClaudeAI EU consumer-protection thread (139 score, 2026-05-07) flags an unresolved compliance angle for EU subscribers — Claude Pro usage limits may not be legally disclosed under EU consumer-protection law. Noted as adjacent context, not part of this announcement.

Open Questions

  • Tier-bump latency. Are existing API accounts auto-bumped to the new tier ceilings, or does Anthropic adjust on a rolling basis? Sources don’t specify.
  • Cowork session limits. No announcement about Cowork-specific limits at the conference. The session-limit changes were framed around Claude Code + API.
  • Managed Agents impact. The same conference announced Managed Agents updates (multi-agent + outcomes + webhooks — covered in Cookbook updates). Source notes “I’m not going to cover that right now” — open thread for a follow-up article.
  • Effective date of Goldman Sachs JV / Blackstone deals. Announced day-before the conference; commercial impact on enterprise customers not disclosed.

Graph View

Backlinks