Last Verified: October 27, 2026 — read live from Claude Code’s own docs (interactive-mode, errors) and support.claude.com, not summarized from memory
You hit your Claude Code usage limit mid-task. Old habit: close the laptop, come back later, retype what you wanted. Since Claude Code v2.1.234, that’s not what happens if you leave the session open — Claude Code waits, and picks the task back up on its own once the limit resets.
In this guide: what shows on screen · what happens at the reset · session limit vs. weekly limit · if it hits the limit again · how to cancel or turn it off · when it won’t wait on its own · FAQ
Quick Start
- What it is: auto-continue, a built-in Claude Code behavior (not a plugin, not a skill you install).
- Who made it: Anthropic — it ships inside Claude Code itself.
- Cost: free, included with your existing Pro or Max subscription.
- Requires: Claude Code v2.1.234 or later, and an interactive session signed in with a claude.ai subscription (per the docs).
- On by default. You don’t turn it on; you can turn it off (see below).
On this page (9 sections)
What Shows on Screen
Hit a limit mid-task and the bottom of the session shows two lines (exact wording, from the docs):
Usage limit reached · limit resets 3:45pm
Continuing automatically at 3:45pm · esc to cancelEither line can carry more after those words — a help link on the first, or /usage-credits to continue now on the second. The conversation itself also logs a line reading Usage limit reached · continuing automatically at 3:45pm · esc to cancel.
The limit message itself comes from a short, fixed list
Per the errors reference, the headline strings are exactly You've hit your session limit and You've hit your weekly limit (plus separate ones for Opus/Sonnet-specific and spend limits). What you’re reading above is what happens after one of those fires, while Claude Code waits it out.
What Happens at the Reset
Keep the session open and, per the docs, the wait resolves itself in order:
| Moment | What appears |
|---|---|
| Reset time arrives | Continuing shortly · esc to cancel |
| Right after | Usage limit reset · continuing automatically appears in the conversation, and Claude Code prompts Claude to pick the task up where it stopped |
| Computer slept >~30 min through the reset | Your usage limit has reset / Press enter to continue — you press Enter yourself. A shorter sleep, or one that ends before the reset, still continues on its own |
It doesn’t resend your last message
The continuation is Claude Code prompting Claude to pick the task up where it stopped — not a re-send of whatever you last typed. The continued turn runs like any other: it still asks for permissions as usual, so it can stop on a prompt while you’re away.
Session Limit vs. Weekly Limit
Two different caps, per Claude’s support article:
| Limit | What it is |
|---|---|
| Five-hour session limit | Both Pro and Max plans have one. All activity in Claude and Claude Code counts toward it |
| Weekly limit | Also on both plans; Max has a separate weekly limit for Fable on top of it |
| “Usage limit reached · wrapping up” | A different, smaller allowance: if you hit the five-hour limit partway through a response already in progress, Claude Code may keep working briefly to finish that step. It’s small and capped, counts toward your weekly limit, and doesn’t apply to new messages sent after the limit. Pro gets this up to once per weekly period; Max can get it each time it hits a five-hour limit. Per the article, it’s rolling out gradually and may not be on every account yet |
That last row is easy to mix up with auto-continue above — they’re not the same thing. “Wrapping up” finishes the current step before the limit fully stops you; auto-continue is what happens after you’re fully stopped, waiting for the reset.
If It Hits the Limit Again
Auto-continue doesn’t retry forever. Per the docs, Claude Code re-arms the wait on its own at most twice in a row. After that it stops and shows:
Automatic continue stopped after repeated usage-limit hits · /rate-limit-options to try againHow to Cancel or Turn It Off
| You want to… | Do this |
|---|---|
| Cancel just this one wait | Press Esc at an empty prompt, or Ctrl+C, while the lines are showing — or run /rate-limit-options and pick Don’t continue automatically. Claude Code confirms with a line starting Automatic continue cancelled |
| Turn it off for good | In /config, turn off Continue automatically at usage limit, or set autoContinueAtUsageLimit to false in your settings file. /config autoContinueAtUsageLimit=false also works |
The key=value shortcut only turns it off
Per the docs, /config autoContinueAtUsageLimit=false can’t turn it back on that way, because the setting grants Claude Code unattended execution while you’re away. Flip it back on from /config itself.
A cancelled wait doesn’t restart itself for that reset window — send a prompt, or pick Wait here, then continue automatically from /rate-limit-options again.
When It Won’t Wait on Its Own
Per the docs, Claude Code doesn’t start the wait automatically in a few cases:
- Remote Control and agent-team teammate sessions — a person at that terminal can still start one
- A reset more than 24 hours away — a weekly limit can reset days out
- An Opus or Sonnet limit while you’re running a different model family — your next turn may not even hit that limit
In those cases, and whenever auto-continue is off, Claude Code opens the usage-limit options menu once per reset window instead; pick Wait here, then continue automatically to start the wait yourself.
Honest Limits
- It needs a claude.ai subscription sign-in in an interactive session. That’s the scope the docs state; this page doesn’t cover every sign-in or automation setup.
- “Wrapping up” and auto-continue are two different features covered by two different support pages — don’t read one as proof of the other.
- The wrapping-up allowance is still rolling out per Anthropic’s own article, so it may not show on your account yet.
- We didn’t trigger a real limit to screenshot it. The quoted lines above are the docs’ own verbatim text, not our screen capture.
FAQ
Do I have to do anything to turn this on?
No. Per the docs, automatic continue is on by default in interactive sessions signed in with a claude.ai subscription, on Claude Code v2.1.234 or later.
Does it resend my last prompt when it continues?
No. At the reset, Claude Code prompts Claude to pick the task up where it stopped; it doesn’t resend your last message.
Will it keep trying forever if I keep hitting the limit?
No. It re-arms itself at most twice in a row, then stops and tells you to run /rate-limit-options to try again.
Can it ask for permission while I’m away?
Yes. The continued turn runs like any other turn, including permission prompts, so it can stop and wait for you.
What if my laptop was asleep when the limit reset?
If it slept more than about 30 minutes through the reset, Claude Code shows Press enter to continue instead of continuing on its own.
Sources
- code.claude.com/docs/en/interactive-mode — “Wait for a usage limit to reset” (status lines, cancel, settings)
- code.claude.com/docs/en/errors — usage-limit message strings
- support.claude.com — five-hour session limit, weekly limit, “wrapping up” allowance