Claude Code / Claude Pro / MaxYou’ve reached your 5-hour usage limit

Claude Code "5-Hour Usage Limit Reached": Recovery Time & Fixes

DIRECT ANSWER

Claude enforces a 5-hour rolling session window starting from the first message of the active cycle—not 5 hours after the rate-limit error appeared.

Open Claude 5-Hour Recovery Calculator →

Why this happens

  • Long uncompacted sessions resend tens of thousands of context tokens on every turn, draining the 5-hour cap rapidly.
  • Assuming the 5-hour timer begins when you hit the error rather than when the first request in that window was sent.
  • Running parallel Claude Code sessions across multiple terminals sharing the same account quota.

Step-by-step fix

  1. 1. Find your window start and compute recovery

    Check your client logs for the timestamp of the first prompt in the active burst and enter it into the WhenReset Claude 5-hour calculator.

  2. 2. Check for global reset events

    Verify on the WhenReset Claude Radar whether Anthropic recently issued an all-user global reset or incident recovery.

  3. 3. Compact or reset context between tasks

    Run /compact or start a fresh session after each completed subtask to stop re-sending stale context on every turn.

Frequently Asked Questions

Why did my Claude quota recover only 2 hours after hitting the limit?

Because your first request in that cycle occurred 3 hours before you hit the cap, leaving only 2 hours until the 5-hour rolling window elapsed.

Does switching from Opus to Sonnet bypass the 5-hour limit?

They share the same account session pool, though lighter models consume quota much more slowly per turn during routine edits.

Related troubleshooting guides