Claude Code Rate Limits Explained — and How to Eliminate Them

How Claude Code Rate Limits Work

Anthropic applies rate limits to Claude Code through multiple overlapping windows. Understanding these is key to knowing why you keep getting locked out.

5-Hour Rolling Window

Every request you make consumes tokens from a 5-hour rolling budget. Once you exhaust your allocation within any 5-hour period, you're locked out until older requests fall outside the window. This is the limit most developers hit during intensive coding sessions.

7-Day Rolling Cap

Even if you pace your 5-hour usage carefully, there's a weekly cap that limits total consumption over a 7-day period. Heavy users typically hit this by Wednesday or Thursday, leaving the rest of the week throttled.

Weekly Opus Cap

Claude Opus (the most capable model) has its own separate weekly limit that's more restrictive than Sonnet. If you rely on Opus for complex reasoning tasks, you'll burn through this budget quickly.

Rate Limits by Plan

Anthropic offers several subscription tiers, each with different limits. Here's how they compare:

What Happens When You Hit a Limit

When you reach a rate limit in Claude Code, several things happen:

• Your current request is rejected with a rate limit error
• You're placed in a cooldown period that can last from minutes to hours
• Claude Code may automatically downgrade you to a less capable model (e.g., Haiku instead of Sonnet)
• Extended thinking requests are the first to be throttled
• Your flow state is broken — context is lost, momentum is killed

For professional developers, this isn't just annoying — it's expensive. A 4-hour cooldown in the middle of a feature can cost you an entire day of productivity.

How OpenLimits Eliminates Rate Limits

OpenLimits is an Anthropic API proxy that pools multiple provider accounts. Instead of routing all your requests through a single account's rate limits, OpenLimits distributes them across a pool of accounts with automatic failover.

How It Works

• Your requests are routed through a pool of Anthropic OAuth accounts
• Each account's utilization is tracked across all rate limit buckets (5-hour, 7-day, Opus)
• Users are split evenly across eligible accounts
• If any account hits a rate limit, it's automatically cooled down and traffic shifts to others
• Stable user-account assignment keeps routing predictable while accounts are healthy

The result: you never see a rate limit. No cooldowns, no throttling, no model downgrades.

Setup Takes 30 Seconds

Add two environment variables to your shell profile:

export ANTHROPIC_BASE_URL=https://openlimits.app
export ANTHROPIC_API_KEY=your-openlimits-key

Every Claude Code session automatically routes through OpenLimits. Extended thinking, streaming, tool use — everything works exactly as before, without limits.

Frequently Asked Questions

Does OpenLimits work with Claude Code CLI?

Yes. Set the two environment variables above and every Claude Code session will route through OpenLimits automatically. No configuration files to edit.

What models are available?

All Claude models: Opus, Sonnet, and Haiku. You can switch between them freely with no separate limits per model.

Is there any added latency?

OpenLimits runs on dedicated VPS infrastructure and preserves streaming behavior expected by Claude-compatible clients.

What about Conductor and other tools?

Any tool that supports ANTHROPIC_BASE_URL works with OpenLimits: Claude Code, Cursor, Conductor, OpenCode, OpenClaw, and any Anthropic SDK client.