Effective May 6, Anthropic doubled the Claude Code 5-hour rate limits for Pro/Max/Team/enterprise plans. Peak-hour reductions are gone for Pro/Max. SpaceX compute deal (220K GPUs at Colossus 1) is what made this possible. The discussion I’m seeing is mostly “finally, I can do longer coding sessions.” Which is true. But for anyone running Claude Code in agent-mode workflows (multi-file refactors, autonomous test loops, long-running planning sessions), there’s a second-order effect worth thinking about. Tight rate limits implicitly capped your spend. When the platform stopped you at request N, your bill was capped at the cost of N requests. The limit was annoying but it was also a guardrail. With doubled limits, the guardrail is much weaker. An autonomous Claude Code session that fan-outs aggressively (parallel file edits, multi-attempt retries on failed tests, branching exploration) can now run materially longer and burn materially more before hitting any platform cap. Most teams haven’t recalibrated their budget assumptions for this. Things worth checking before next week: Spend alerts at the API console level. Set them, then update the thresholds because the previous numbers were calibrated for the old limits. Retry budgets in any agentic loops. “Try until passing” behaved one way when capped at the old limit, behaves differently with 2x headroom. The –max-turns or equivalent setting in any wrapper scripts. Reflect the new ceiling explicitly rather than relying on platform limits. If you’re routing through a proxy, today’s a good day to verify per-key budget caps are configured. Bifrost ( i use this its oss ), LiteLLM, and Cloudflare AI Gateway all do hard cost enforcement at the gateway. The platform isn’t your backstop anymore. Higher limits are a real win for productive work. They also exposed an implicit cost-control I’d been relying on without realizing it. submitted by /u/llamacoded
Originally posted by u/llamacoded on r/ClaudeCode