Home / Guides / Claude Code Rate Limits

Claude Code Rate Limits Explained: The 5-Hour Window

Everything you need to know about Anthropic Claude Code rate limits — how the rolling 5-hour window works, Pro vs Max plan differences, and how to prevent lockouts.

Last updated March 2026 · By Soren Starck

What Are Claude Code Rate Limits?

Anthropic's Claude Code enforces rate limits that cap how much you can use the tool within a given time period. These limits vary by plan and exist to manage server capacity and ensure fair usage.

The key concept is the 5-hour rolling window. Unlike a daily cap that resets at midnight, Claude Code uses a sliding window — the tokens you used exactly 5 hours ago start becoming available again, continuously.

Pro vs Max Plan Limits

Your rate limit depends on your Anthropic subscription plan:

PlanPriceRate LimitBest For
Pro$20/monthStandardLight to moderate usage
Max 5x$100/month5x Pro limitsRegular daily coding
Max 20x$200/month20x Pro limitsHeavy professional use

Even on the Max plan, rate limits still apply — they're just higher. Monitoring is valuable at every plan level because hitting the limit is always disruptive.

How the 5-Hour Rolling Window Works

The 5-hour window is a sliding limit. Imagine a conveyor belt where tokens enter one end and fall off (become available again) exactly 5 hours later.

Example Timeline

TimeActionUsage
9:00 AMStart coding session0%
10:00 AMHeavy refactoring with Claude Code40%
11:30 AMBug fixing session75%
12:00 PMClaude shows “90% of session limit”90%
12:15 PMRate limit hit — locked out100%
2:00 PM9 AM usage rolls off — capacity returns~60%

What “90% of Session Limit” Means

When Claude Code shows you are at 90% of your session limit, it means you've used 90% of your allotted tokens in the current 5-hour rolling window. You're close to being locked out.

The problem: Claude only shows this warning when you're already dangerously close. By the time you see “90%”, you may only have a few prompts left before getting locked out.

SessionWatcher shows your usage percentage continuously — at 30%, 50%, 70% — so you can pace your work long before you approach the limit.

See your rate limit status at all times.

SessionWatcher for Claude Code shows your real-time usage percentage, 5-hour window countdown, and sends macOS notifications before you hit the limit. $1.99 one-time, no subscription.

What Happens When You Hit the Limit

  • Claude Code stops responding — your requests are rejected
  • No clear ETA — the rolling nature makes it hard to know when you can resume
  • Late warning — by the time you see “90%”, you're almost out
  • Lost momentum — you break your coding flow and lose context

Tips for Managing Claude Code Rate Limits

  1. Monitor usage in real-time — use SessionWatcher to see your exact position in the 5-hour window
  2. Front-load heavy tasks — do token-intensive work at the start of your window
  3. Be specific in prompts — targeted prompts use fewer tokens
  4. Pace heavy sessions — if you're at 70% with 3 hours left, switch to lighter tasks
  5. Consider upgrading — if you consistently hit Pro limits, the Max plan gives 5x or 20x the capacity

Frequently Asked Questions

What are Claude Code rate limits?

Usage caps on a rolling 5-hour window that limit the number of tokens you can use. They vary by plan (Pro, Max 5x, Max 20x). When you hit the limit, Claude Code stops responding.

How long until my Claude Code rate limit resets?

It's a rolling window, not a fixed reset. Tokens from 5 hours ago start becoming available continuously. SessionWatcher tracks this in real-time.

How do session limits work in Claude?

Session limits are based on a rolling 5-hour window of token usage. Your limit depends on your plan. As you use tokens, your quota decreases. After 5 hours, the earliest tokens start freeing up — it's a continuous process, not a fixed reset.

Should I upgrade from Pro to Max?

If you consistently hit your rate limits and lose productivity, upgrading gives you significantly more capacity. But first, try monitoring with SessionWatcher — you may find that pacing your usage on Pro is sufficient.