"Usage limit reached · continuing automatically at {time} · esc to cancel"
by vortwangUpdated
"Usage limit reached · continuing automatically at {time} · esc to cancel" is not an error: Claude Code (v2.1.234 or later) hit your claude.ai session or weekly limit and is waiting in the open session to continue the task after the reset. The time shown is your own reset clock, the same one /usage shows. Press Esc at an empty prompt to cancel. It is unrelated to the account-wide resets this board records.
- Last reset
- 04 SEP 20:08Z
- Status
- OVERDUE
The gap since the last reset is past 1.5x the recent median.
- Next est.
- ANY TIME
- Days since
- 14.4
days
What does "Usage limit reached · continuing automatically at {time} · esc to cancel" mean?
Since v2.1.234, Claude Code "continues your session automatically when a claude.ai usage limit resets". The Interactive mode docs describe the line you see while it waits: "Usage limit reached · continuing automatically at 3:45pm · esc to cancel". Automatic continue is on by default in interactive sessions signed in with a claude.ai subscription.
The follow-up lines are documented too. At the reset the line reads "continuing shortly", then "Usage limit reset · continuing automatically", and Claude Code sends Claude a fixed prompt to pick the task up where it stopped; it does not resend your last message. If your computer slept for more than about 30 minutes and the limit reset meanwhile, it reads "Your usage limit has reset · press enter to continue".
There is a cap. If the continued task hits the limit again, Claude Code re-arms the wait "at most twice in a row", then stops with "Automatic continue stopped after repeated usage-limit hits · /rate-limit-options to try again". Cancelling with Esc or Ctrl+C prints a line that starts "Automatic continue cancelled".
Which window is full?
| Window | Resets | Where to check |
|---|---|---|
| Session limit (5-hour) | Every five hours; the exact time is the one in the message | /usage in Claude Code, or Settings > Usage on claude.ai |
| Weekly limit | At a fixed time each week that is assigned to your account | /usage in Claude Code, or Settings > Usage on claude.ai |
What to do when you see it
- Leave the session open
The docs say to keep the session open; the wait ends if you exit Claude Code, and it does not restart when you resume the session. Permission prompts still fire as usual, so the task can pause on one while you are away.
- Or cancel with Esc
Press Esc at an empty prompt, or Ctrl+C, while the line shows, or run /rate-limit-options and pick "Don't continue automatically". Sending any prompt also ends the wait and runs your prompt instead.
- Finish early with usage credits or another model
When you finish adding usage credits with /usage-credits, sign back in after /upgrade, or switch models with /model during the wait, Claude Code checks whether usage is available again and continues right away. A purchase made in a browser on your own is not detected.
- Check the clock with /usage
The time in the line is your session or weekly reset; /usage shows the same bars. A weekly limit can be days out, and Claude Code does not start the wait on its own when the reset is more than 24 hours away.
- Turn it off if you prefer the menu
In /config turn off "Continue automatically at usage limit", or set autoContinueAtUsageLimit to false in user settings. With it off, Claude Code opens the usage-limit options menu once per reset window instead, and you can still pick "Wait here, then continue automatically".
When does it reset?
Your own window: the line names the time your session limit (every five hours) or weekly limit (a fixed weekly time assigned to your account) resets. /usage shows the same clocks. Put the time on a countdown with the window tracker linked below.
Account-wide resets: separately, Anthropic sometimes resets 5-hour and weekly limits for everyone at once. Those are what this board records, each linked to its original post, and the row above shows the last one. They are announced, not scheduled, so this site does not promise one.
Related errors
FAQ
Is "continuing automatically" an error?
No. It is the status line Claude Code shows while it waits for your claude.ai usage limit to reset, a feature added in v2.1.234. Nothing failed; the interrupted task resumes after the reset unless you cancel with Esc or send a prompt.
Why did it stop after a few resets?
If the continued task hits the limit again, Claude Code re-arms the wait at most twice in a row, then shows "Automatic continue stopped after repeated usage-limit hits · /rate-limit-options to try again". Run /rate-limit-options and pick the "Wait here, then continue automatically" row to start another wait.
Why did my session not continue?
The docs list cases where the wait does not start on its own: Remote Control and agent-team teammate sessions, a reset more than 24 hours away, an Opus or Sonnet limit while you run a model outside that family, background sessions and -p runs, API keys and cloud providers. Users have also reported it not firing in a detached tmux session (issue #91535) and being offered in only one of several concurrent sessions (issues #92004, #92418).
How do I turn automatic continue off?
In /config, turn off "Continue automatically at usage limit", or set autoContinueAtUsageLimit to false in your user settings. The settings reference says the default is true and the key is read from user, --settings and managed settings only. The Desktop app's "Auto-continue when limits reset" checkbox is a separate switch.
Sources
- Claude Code docs: Interactive mode — Wait for a usage limit to resetverified 2026-09-18
- Claude Code docs: Error reference — "You've hit your session limit"verified 2026-09-18
- anthropics/claude-code CHANGELOG.md — 2.1.234 "continues your session automatically when a claude.ai usage limit resets"; 2.1.271 dynamic workflows pauseverified 2026-09-18
- Claude Code docs: Settings reference — autoContinueAtUsageLimit (default true; User or managed scope)verified 2026-09-18
- Claude Code docs: Slash commands — /rate-limit-options, /usage, /usage-credits, /statusverified 2026-09-18
- anthropics/claude-code issue #92418 (2026-09-06): Auto-continue disabled after five_hour rate limit reset with multiple sessionsverified 2026-09-17
- anthropics/claude-code issue #91535 (2026-09-02): Auto-continue after usage-limit reset (2.1.234+) doesn't fire in a detached tmux sessionverified 2026-09-17
- anthropics/claude-code issue #92004 (2026-09-04): Auto-continue at usage-limit reset is offered in only one sessionverified 2026-09-17
Want the next Claude reset on your phone?