Hit Your Usage Limit Tonight? Keep the Session Open and Claude Continues at the Reset.

At a glance

• Since v2.1.234, an interactive Claude Code session on a claude.ai subscription waits out a usage limit and continues the task after the reset, if you leave it open.
• It is on by default, but a project settings file, a permission prompt or a sleeping machine can stop it quietly.
• When the wait does not start on its own, /rate-limit-options starts it by hand. The Desktop Code tab has its own checkbox.

You start a long refactor at 10 PM. Claude gets halfway, and the session stops with You've hit your session limit and a 1:00am reset. Claude Code can hold that session open, wait for the reset and pick the task back up while you sleep, if a few quiet conditions hold.

Why it matters

Automatic continue turns the dead hours after a limit into work, but only if the session stays open, the machine stays awake and no setting has turned it off. The continued turn still asks for permissions as usual, so a task can stall on a prompt at 2 AM and look like the feature failed.

How to let a session continue after the reset

At 4:10 PM ET on 8 October 2026, npm stable was v2.1.286 and latest and next were v2.1.295, so every npm channel clears the v2.1.234 floor.

1. Run claude --version and confirm v2.1.234 or later. Run /status and confirm the account is your claude.ai login. The docs say API keys, cloud providers and usage-based billing get no wait.
2. Open /config and confirm Continue automatically at usage limit is on. If the row is missing, managed settings or the --settings flag already set the key.
3. Check your project files. autoContinueAtUsageLimit is read only from user settings, --settings and managed settings. When none of those set it, a project or local settings file that sets it turns the feature off instead of being ignored.
4. Start in a permission mode you trust, because a permission prompt stops the continued turn until you answer.
5. Leave the terminal open and keep the machine awake. If it sleeps for more than about 30 minutes and the limit resets during that sleep, Claude Code waits for you to press Enter.
6. When the limit hits, look for Continuing automatically at 1:00am and esc to cancel, and leave the prompt empty, since a prompt you send replaces the wait.

# Needs v2.1.234 or later; every npm channel has it today
claude --version
# A hit in a project or local .claude/ file switches the feature off
grep -sn autoContinueAtUsageLimit ~/.claude/settings.json .claude/settings.json .claude/settings.local.json
# Keep the machine awake: start the session with ONE of these
# macOS (idle sleep only, not lid close):
# caffeinate -i claude
# Linux with systemd:
# systemd-inhibit --what=idle:sleep claude

# Needs v2.1.234 or later; every npm channel has it today
claude --version
# A hit in a project or local .claude/ file switches the feature off
grep -sn autoContinueAtUsageLimit ~/.claude/settings.json .claude/settings.json .claude/settings.local.json
# Keep the machine awake: start the session with ONE of these
# macOS (idle sleep only, not lid close):
# caffeinate -i claude
# Linux with systemd:
# systemd-inhibit --what=idle:sleep claude

At the reset, the conversation shows Usage limit reset with continuing automatically, and Claude picks the task up where it stopped. This tip is from the docs; we did not wait out a live limit, so treat your first night as the test.

When it does not start on its own

Claude Code skips the automatic wait when the reset is more than 24 hours away (a weekly limit can be days out), in Remote Control and agent team teammate sessions, and for an Opus or Sonnet limit while you run a model outside that family. In those cases, or with the setting off, run /rate-limit-options and pick Wait here, then continue automatically.

Claude Desktop

In the Desktop Code tab, the session limit card offers an Auto-continue when limits reset checkbox, and Desktop then retries the interrupted turn after the reset. The weekly limit card does not offer it. It is separate from the terminal setting, so turn each off on its own.

Gotchas

• What ends the wait: exiting Claude Code (resuming does not restart it), switching accounts, clearing the conversation, /resume to another session, or handing the session to Desktop, a background session or the cloud.
• Repeat hits: Claude Code re-arms the wait at most twice in a row, then points you to /rate-limit-options.
• Not for unattended runs: -p runs and background sessions do not get the wait.
• Lid close: caffeinate does not stop lid-close sleep on a Mac.
• Opting out: set autoContinueAtUsageLimit to false in user settings. The inline /config autoContinueAtUsageLimit=false form can turn it off but cannot turn it back on.

Recommended AI prompt

Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use.

I use Claude Code in the terminal and the Claude Desktop Code tab on a claude.ai subscription, and I want a long task to continue on its own after a session usage limit resets overnight. Ask for my operating system and the output of claude --version first, and if it is older than v2.1.234, tell me the feature is missing. Then, using only the documented automatic continue feature (the Continue automatically at usage limit row in /config, the autoContinueAtUsageLimit setting, /rate-limit-options, and the separate Desktop Auto-continue when limits reset checkbox), give me a five-minute pre-bed checklist: confirm my login with /status, find any project settings file quietly turning it off, avoid stalling on a permission prompt, keep my machine awake, and list what cancels the wait. Do not invent settings or commands.