How Claude Code waits for a usage limit to reset and continues automatically

by vortwangUpdated Sep 18, 2026

Since Claude Code v2.1.234, when a claude.ai usage limit stops Claude mid-task, Claude Code 'waits in the open session and continues the task on its own after the limit resets'. It is on by default with a subscription; the bottom line reads 'Usage limit reached · continuing automatically at 3:45pm · esc to cancel'. Turn it off in /config ('Continue automatically at usage limit') or with autoContinueAtUsageLimit: false. It re-arms at most twice in a row and is never offered for -p runs or API keys.

What the official docs say

Claude Code waits in the open session and continues the task on its own after the limit resets.
Quoted from Claude Code docs: Interactive mode — Wait for a usage limit to reset (what you see, cancel, start a wait yourself, turn it off)
Automatic continue is on by default in interactive sessions signed in with a claude.ai subscription. Requires Claude Code v2.1.234 or later.
Quoted from Claude Code docs: Interactive mode — Wait for a usage limit to reset (what you see, cancel, start a wait yourself, turn it off)
If it hits the limit again, Claude Code re-arms the wait on its own at most twice in a row
Quoted from Claude Code docs: Interactive mode — Wait for a usage limit to reset (what you see, cancel, start a wait yourself, turn it off)
In /config, turn off Continue automatically at usage limit, or set autoContinueAtUsageLimit to false in your user settings.
Quoted from Claude Code docs: Interactive mode — Wait for a usage limit to reset (what you see, cancel, start a wait yourself, turn it off)
Claude Code now continues your session automatically when a claude.ai usage limit resets; turn it off in /config
Quoted from anthropics/claude-code CHANGELOG.md — 2.1.234 automatic continue; 2.1.271 dynamic workflows pause and continue (read 2026-09-18, latest 2.1.276)
Improved dynamic workflows to pause when you hit your usage limit and continue automatically when it resets
Quoted from anthropics/claude-code CHANGELOG.md — 2.1.234 automatic continue; 2.1.271 dynamic workflows pause and continue (read 2026-09-18, latest 2.1.276)
The Desktop checkbox and the CLI's Continue automatically at usage limit setting in /config are separate, so turn each off on its own.
Quoted from Claude Code docs: Error reference — "You've hit your session limit" (Desktop Auto-continue checkbox; 85% warning; rate_limits in the status line)

Steps

What it does. The interactive-mode docs: 'When a claude.ai usage limit stops Claude mid-task, Claude Code waits in the open session and continues the task on its own after the limit resets.' At the reset it sends Claude 'a fixed prompt to pick the task up where it stopped. It doesn't resend your last message.' The continued task 'runs like any other turn', so it can still stop on a permission prompt while you are away. The changelog entry for 2.1.234 introduced it; 2.1.271 extended the same pause-and-continue to dynamic workflows 'instead of dropping the affected agents'.

When it is not offered. Claude Code does not start a wait on its own in Remote Control and agent-team teammate sessions, when a reset is more than 24 hours away (a weekly limit can be), or for an Opus or Sonnet limit while you run a model outside that family. It never offers the wait for background sessions and -p runs, for API keys, cloud providers and usage-based billing ('there is no reset to wait for'), or through an LLM gateway without a saved claude.ai login. Users also report it not firing in a detached tmux session (#91535) and being offered in only one of several concurrent sessions (#92004, #92418); those are user reports on the official repository, not documented behavior.

Related but separate. The Desktop app's session-limit card has its own 'Auto-continue when limits reset' checkbox: 'The Desktop checkbox and the CLI's Continue automatically at usage limit setting in /config are separate, so turn each off on its own.' Neither moves the reset time; the board above records the only other thing that does, an account-wide reset by Anthropic.

Check your version and sign-in
The wait requires Claude Code v2.1.234 or later and an interactive session signed in with a claude.ai subscription. /status opens the Status tab with version and account. On API keys, cloud providers or usage-based billing the feature is not offered because usage is metered per request.
Hit a limit and keep the session open
With automatic continue on (the default), a line at the bottom of the session reads 'Usage limit reached · continuing automatically at 3:45pm · esc to cancel', with your own reset time. Keep the terminal open; if you exit Claude Code, the wait does not restart when you resume the session.
Read what happens at the reset
At the reset the line reads 'continuing shortly', then 'Usage limit reset · continuing automatically', and Claude picks the task up from a fixed prompt. If your computer slept for more than about 30 minutes and the limit reset while it slept, the line reads 'Your usage limit has reset · press enter to continue'; press Enter.
Continue early if you add usage
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 and continues right away. It does not check after an upgrade or purchase you make in a browser on your own.
Cancel a wait
Press Esc at an empty prompt, or Ctrl+C, while the line shows, or run /rate-limit-options and pick 'Don't continue automatically'. Claude Code confirms with a line that starts 'Automatic continue cancelled'. After a cancel nothing continues until you send a prompt or pick 'Wait here, then continue automatically' again; the next reset window starts fresh.
Start a wait yourself when it is not automatic
In a Remote Control or agent-team teammate session, when the reset is more than 24 hours away, or whenever automatic continue is off, run /rate-limit-options (type it in full; it is not in the command menu) and pick the row that starts 'Wait here, then continue automatically'. A wait you picked yourself keeps counting down even if the setting turns off.
Turn automatic continue off, and know when it stops on its own
In /config turn off 'Continue automatically at usage limit', or set autoContinueAtUsageLimit to false in user settings; '/config autoContinueAtUsageLimit=false' also works, but the key=value form cannot turn it back on. If the continued task hits the limit again, Claude Code re-arms at most twice in a row, then shows 'Automatic continue stopped after repeated usage-limit hits · /rate-limit-options to try again'.

FAQ

Does automatic continue reset my limit sooner?

No. It waits for the reset time shown in the message, which is your own session or weekly clock, and then continues. The only things that refresh a limit early are usage credits, which let you keep working without moving the clock, and account-wide resets by Anthropic, which this board records.

Why did Claude Code not wait for my weekly limit?

Claude Code does not start a wait on its own when the reset is more than 24 hours away, and a weekly limit can reset days out. You can still run /rate-limit-options and pick 'Wait here, then continue automatically'; a wait you picked yourself keeps counting down.

Does it work in tmux or with several sessions open?

The docs do not address either. Users report on the official repository that the wait does not fire in a detached tmux session (#91535) and that with several sessions open only one is offered the wait (#92004, #92418). Those are user reports; if it matters, keep the waiting session attached and start the wait yourself in each session.

Is the Desktop app checkbox the same setting?

No. The Desktop app's session-limit card offers an 'Auto-continue when limits reset' checkbox (the weekly-limit card does not), and the docs say it and the CLI's /config setting 'are separate, so turn each off on its own'.

Can an admin turn it off for everyone?

Yes. autoContinueAtUsageLimit is read from user settings, --settings and managed settings; when set by managed settings or the --settings flag, the /config row is hidden. A project or local settings file that sets it turns the feature off rather than being ignored.

Sources

Want the next Claude reset on your phone?

Get alerted Page me