You’re mid-refactor and the session stops with “You’ve hit your session limit”. Claude Code limits got worse before they got better in 2026: on May 6, Anthropic doubled the 5-hour limits for Pro, Max, Team and seat-based Enterprise. The other half of the story is how much quota goes to context you never look at, from MCP servers to subagents.
How Claude Code rate limits actually work
Claude Code doesn’t run on a single quota. It runs on two independent gates stacked on top of each other, as Anthropic’s Claude Code usage-limits help page explains: a 5-hour session limit that resets five hours after your first message in a session, and a weekly limit. Hit either one and you’re throttled. Being nowhere near your weekly cap doesn’t help you if you’ve blown through the 5-hour window in one long session.
The part that trips people up: on Pro and Max plans, that usage pool isn’t exclusive to Claude Code. Claude.ai chat sessions, Claude Desktop and Cowork draw from the same shared budget, per Anthropic’s usage and length limits article. Spend an hour brainstorming with Claude.ai in the morning and you’ve already eaten into the allowance you meant to use for an afternoon coding session, because there’s no separate “coding” meter.
Anthropic doesn’t publish hour counts for either limit. Usage depends on conversation length, the features you use, the model and the effort level, so the same plan can last a full workday for one developer and a single morning for another.
The 2026 rate limit timeline: what actually happened
If you hit a wall with Claude Code sometime between March and May of 2026, it wasn’t your imagination. The change that matters today came on May 6, 2026.
May 6, 2026: the permanent fix. In its May 6 announcement, Anthropic doubled Claude Code’s 5-hour limits for Pro, Max, Team, and seat-based Enterprise plans, and removed the peak-hour limit reduction for Pro/Max entirely. The announcement doesn’t mention weekly limits, and the Free plan still has no Claude Code access. Anthropic tied the capacity increase to new compute: a SpaceX deal for 300+ MW (220,000+ NVIDIA GPUs at the Colossus 1 cluster), an Amazon agreement for up to 5 GW, and a Google deal with capacity starting in 2027.
Current Claude Code limits by plan
Anthropic doesn’t publish prompt, token or hour counts per plan. Claude’s pricing page states each plan’s allowance as a multiple of Pro, so that’s what the table shows. Actual usage still varies with prompt length, context size, model choice and effort.
| Plan | Price | 5-Hour Limit | Weekly Limit |
|---|---|---|---|
| Pro | $20/mo | Baseline (1x) | Baseline (1x), no separate Fable limit |
| Max | $100/mo | 5x Pro | 5x Pro, plus a separate Fable weekly limit |
| Ultra | $200/mo | No 5-hour limit (verified accounts) | 10x Pro |
| API (pay-as-you-go) | Per-token | Tier-based requests/tokens per minute, not session-based | No weekly cap, billed per token |
Plan allowances from Claude’s pricing page and Help Center, checked November 1, 2026.
The Pro/Max split matters more than the headline numbers suggest. Anthropic’s help pages describe weekly limits that apply across all models, not separate Sonnet and Opus buckets. The one documented separate bucket is a weekly limit for Fable models on Max; Pro has none. Model choice still matters, because heavier models use up the shared limit faster.
The real reason you’re hitting Claude Code rate limits
Plan math explains part of the picture. It doesn’t explain why two developers on the same Max plan can have wildly different experiences, with one cruising through a full workday and the other hitting a wall by lunch. The gap usually comes down to three things, and the first one is easy to miss.
MCP servers still add overhead. Per Claude Code’s cost docs, MCP tool definitions are deferred by default, so only tool names and server instructions enter context until Claude uses a specific tool. That depends on tool search, which is on by default on supported models but off on some, such as Google Cloud Agent Platform models older than Opus 4.5, Sonnet 4.5 and Haiku 4.5; there, full definitions load up front. Run /context to see what’s using space and /mcp to disable servers you don’t use.
Subagents add their own usage. A subagent’s own requests still draw on your usage, and a subagent can fail with a “Prompt is too long” error. Subagents also start cold, so they frequently re-read files the parent session already loaded, which duplicates token cost.
Model choice and session length compound it. Opus burns through allowance faster than Sonnet, and Claude Code’s docs note that Sonnet handles most coding tasks well and costs less than Opus. Long, unmanaged sessions accumulate stale conversation history, and every resend of that bloated context re-costs tokens. Prompt caching offsets some of this, but only for the portion of the prompt that’s actually cached.
If you want one number to check today: open a fresh Claude Code session, look at how many MCP servers auto-connect, and ask whether you’ve actually used all of them this week. Most developers haven’t.
How to work around Claude Code rate limits
Some workarounds are just good hygiene, and one is a genuine Terms of Service gray area. Ranked roughly by legitimacy and impact:
1. Proactive context hygiene. Claude Code’s guide to reducing token usage covers both commands below. Run /compact at natural checkpoints (after finishing a refactor, fixing a bug, before starting a new module) to compress history while keeping the decisions that matter. Use /clear when you’re switching to a genuinely unrelated task, or when the context is “poisoned” by an assumption Claude keeps reverting to; /clear wipes conversation history but keeps the code changes already made. Anything that has to survive a compaction (architectural decisions, non-obvious constraints) belongs in CLAUDE.md or another file that gets deterministically re-read, not left to a lossy auto-summary.
2. Let prompt caching actually work for you. Claude Code caches automatically when a session resends the same context prefix, and Anthropic’s API pricing page puts a cache hit at 10% of the standard input price (5% on Sonnet 5.5 and Opus 5.5). The practical rule: keep stable content (system instructions, CLAUDE.md, background context) at the very start of the prompt, and don’t let gaps between messages exceed the cache TTL, which Claude Code’s prompt-caching docs put at 1 hour for the main conversation on a subscription plan and 5 minutes once a session draws on usage credits or an API key. Miss that window and the next message reprocesses the full context at full cost.
3. Switch models for routine work. Drop from Opus to Sonnet for anything that doesn’t need Opus-level reasoning. On any plan, it slows how fast you drain the weekly limit, which applies across all models.
4. Move to API pay-as-you-go billing. Metered API billing removes the session-based 5-hour and weekly caps in favor of per-token pricing with standard tier-based rate limits. Useful for teams or automation pipelines that need predictable throughput rather than a subscription’s flat ceiling, at the cost of variable spend that needs its own monitoring.
5. Build a multi-tool bench instead of one hard stop. Rather than treating Claude Code as the only option, pair it with something else and switch based on task shape: Claude Code for complex multi-file refactoring, Gemini CLI when a task needs an entire large monorepo in context, Codex CLI for intent-driven single-file work. Our AI coding assistant comparison breaks down how these tools stack up outside of the rate-limit question. If something else can pick up the task, a rate limit on one tool only slows you down. If you’re hitting limits constantly because of heavy, repetitive automation rather than interactive coding, it’s also worth asking whether a self-hosted open-weight model on your own GPU makes more sense for that specific workload. Our guide to self-hosting a coding assistant on a Vultr GPU instance walks through what that setup actually costs.
6. Multi-account switching (use with real caution). Running claude logout then claude login with a different account gives you that account’s independent usage window. This is not an officially sanctioned workflow, and a more aggressive version (using anti-detect browsers to run multiple accounts in parallel) technically violates Anthropic’s Terms of Service, even if enforcement is unclear. Know what you’re trading before you lean on it.
Which workaround should you actually use?
If you only do one thing, do context hygiene. It’s free and low-risk, and it’s the biggest lever most developers haven’t touched. Pair it with an MCP server check: run /context to see what’s using space and /mcp to disable servers you don’t use. If you’re a solo developer on Pro hitting walls mid-session, model switching (Sonnet over Opus for routine work) buys the most runway for the least effort. If you’re running Claude Code inside automation or CI where predictable throughput matters more than flat pricing, API billing is the more defensible move than stacking accounts. Save multi-account switching for genuine emergencies rather than a standing workflow; it’s the one option here with real ToS exposure.
Fix your habits before you fix your plan
Claude Code rate limits got a real, permanent improvement on May 6, 2026: the 5-hour windows doubled, and the peak-hour penalty is gone. But a bigger plan alone won’t fix a rate-limit problem that’s actually a context-management problem. If you’re hitting walls regularly, audit your MCP servers and check /context before you reach for your wallet. Run /compact and /clear deliberately instead of letting sessions bloat for hours, and save Opus for the work that actually needs it. Only after those habits are in place does upgrading plans or switching to API billing start to make sense. And if Claude Code still isn’t enough on its own, pairing it with a second tool is a more sustainable fix than stacking accounts.
