Claude Code Hit a Limit? Auto-Continue Picks Up the Thread
Claude Code now waits for your usage limit to reset and resumes exactly where it stopped — automatically. How it works, and how to turn it on or off.
Evgenii Arsentev · PhDReviewed for accuracy by Evgenii Arsentev, PhD · 2026-10-07
Hitting a usage limit mid-task used to mean one thing: come back later and re-explain everything to Claude. Since v2.1.234 that story changed. Claude Code can now wait for the limit to reset and resume the interrupted turn automatically — no babysitting, no copy-paste archaeology. I'm Evgeny, and this is the feature that let me start a long refactor before leaving for dinner and come back to a finished diff.
What is a Claude Code usage limit?
On subscription plans (Pro, Max, Team, Enterprise), Claude Code draws from a per-seat allowance that resets on two clocks: a rolling five-hour session window and a weekly window. When the session window runs out, you hit the 'You've hit your session limit' card; the weekly window has its own card. In the CLI, auto-continue can wait through either one — automatically when the reset is less than 24 hours away, manually via /rate-limit-options otherwise. On Desktop, only the session-limit card carries the auto-continue checkbox; the weekly card never does. Both cards show when the relevant clock resets.
How does Claude Code auto-continue work?
When a session limit fires, Claude Code shows you the reset time and waits. Once the limit resets, it replays the interrupted turn automatically — picking up the task exactly where it broke off. You do not need to retype the request or even be at the keyboard. The session stays open in the background, and Claude resumes as if the wait never happened. This has been the default behaviour since v2.1.234: the Desktop app additionally shows an 'Auto-continue when limits reset' checkbox right on the limit card, and if automatic continue doesn't kick in on its own, the CLI's /rate-limit-options menu lets you pick 'Wait here, then continue automatically'.
On Desktop, the auto-continue checkbox only appears on the session-limit card, never the weekly one. In the CLI, you can still wait out a weekly limit by picking 'Wait here, then continue automatically' from /rate-limit-options — Claude Code just won't start that wait on its own when the reset is more than 24 hours out. Either way, /usage-credits lets you buy past the wait if you'd rather not sit on it.
How to turn auto-continue on or off
Control auto-continue in three places
- 1In /config: find 'Continue automatically at usage limit' and toggle it. The setting persists across sessions.
- 2In settings.json: add {"autoContinueAtUsageLimit": false} to ~/.claude/settings.json to turn it off globally, or true to keep it on explicitly.
- 3On Desktop: when the limit card appears, check or uncheck 'Auto-continue when limits reset' right on the card — a separate control from the CLI setting above, so toggle both if you use both surfaces.
- 4Organisations on managed settings: admins can lock the behaviour with the autoContinueAtUsageLimit managed-settings key.
{ "autoContinueAtUsageLimit": false }Drop this into ~/.claude/settings.json (or the project-level .claude/settings.json) to disable auto-continue everywhere for that scope. Remove the key or set it to true to re-enable it.
Long tasks — refactoring a big module, running a workflow across dozens of files, researching a complex topic — can easily exceed a session window. With auto-continue on, those tasks just finish, possibly after a pause you never notice. The pattern: start the work, enable auto-continue if needed, walk away. Come back to a result.
Does auto-continue work on Desktop and CLI?
Yes, on both surfaces, from v2.1.234 on. In Claude Code Desktop's Code tab, the limit card shows a checkbox and the retry time when it is armed. In the CLI, no action is needed — Claude Code starts the wait on its own as long as autoContinueAtUsageLimit is not explicitly set to false. Remote Control sessions and claude.ai/code sessions also support it, since they route through the same limit mechanism.
Lab: verify it is on
0/4One thing to keep in mind: while Claude is waiting for the reset, your session is still open. If you close Claude Code (not just background it), the task stops. To be safe, minimise the window rather than quitting — or check if the Desktop app offers 'Move to background', which keeps the session alive even after the window closes.
Free course
Stop reading about AI — start building with it
The free Claude Code course: your first site, tool or game — no coding. No upsells, no cross-sells — nothing to buy here.
Start free →Author
Evgenii Arsentev
PhD · Chief Executive Officer, digital health
Reading is a good start
Want to actually build this?
Guides explain. The free course transforms — personalized, gamified, and built to get you shipping fast.
Start the free course →