Anthropic announced on May 6 that it is doubling Claude Code's five-hour rate limits across Pro, Max, Team, and Enterprise plans, eliminating peak-hour throttling entirely, and raising Claude Opus API rate limits for all developers. The changes are backed by a compute agreement with SpaceX that adds more than 220,000 NVIDIA GPUs and 300 megawatts of capacity from SpaceX's Colossus 1 facility within the month.

What Changed

Three specific limits are updated, effective immediately:

  • Claude Code 5-hour cap doubled: The usage limit that previously paused long coding sessions is now twice what it was for Pro, Max, Team, and seat-based Enterprise plans.
  • Peak-hour throttling removed: Pro and Max accounts previously faced reduced limits during high-traffic hours. That restriction is eliminated across both plans.
  • Opus API rate limits raised: Claude Opus throughput for API customers has been increased considerably. Current numbers are in the rate limits documentation.

Why It Matters for Creators

The peak-hour removal has the most direct day-to-day impact. Anyone running Claude Code for extended creative sessions was previously hitting a hard wall during US business hours. That wall is now gone. For developers building generative tools on the API, the raised Opus limits mean fewer 429 errors during multi-step pipelines (image description chains, content scoring loops, or any workflow calling Opus repeatedly in a short window).

The compute deal also matters as a signal: Anthropic's new GPU capacity is already committed. If you have been holding off on Opus-heavy workflows because of throughput concerns, the infrastructure to support them is now in place. Check your plan tier at claude.com/pricing: Pro, Max, Team, and Enterprise all benefit from today's changes. If you are building creative pipelines with Claude, the Claude Blender Connector walkthrough shows what an end-to-end creative tool integration looks like in practice.

What to Do Next

No action is required to get the higher limits: they apply automatically to qualifying plans. If you have been working around the old Claude Code cap by splitting tasks or scheduling around peak hours, you can remove that overhead. API developers should review their retry logic, since the new Opus limits change the practical ceiling and back-off parameters tuned to the old caps may now be too conservative. The official integration guide is at Claude Code. For a broader view of connecting Claude to creative tools, see our Claude creative workflow connectors guide.