TL;DR When you hit the limit, leave the session open: you'll see
continuing automatically at 3:45pmand the task picks back up at reset. If that line never shows, run/rate-limit-optionsand pick Wait here, then continue automatically. It won't wait on its own when the reset is more than 24 hours out (typical of the weekly limit) or after you close the terminal, and if your laptop sleeps for more than 30 minutes it asks you to press Enter.
Since v2.1.234, when Claude Code stops you mid-task with You've hit your session limit · resets 3:45pm, it no longer sits idle until you come back. It waits in the session and resumes the task shortly after the limit resets. In the terminal it's on by default when you're signed in with a claude.ai subscription (Pro, Max, Team or Enterprise). All you have to do is leave it open.
When each limit resets is covered in the 5-hour window and the weekly cap. This tip is about what happens after the cutoff.
What you see while it waits
You've hit your session limit · resets 3:45pm
Usage limit reached · continuing automatically at 3:45pm · esc to cancel
At the reset time the line changes to continuing shortly, then Usage limit reset · continuing automatically. Claude Code sends Claude a fixed prompt to pick the task up where it stopped. It does not resend your last message.
(The output is the one in the docs. I didn't force a limit to capture it, but the strings are in the v2.1.282 binary.)
How to turn it on
1. In the terminal it's already on. Check it in /config, on the Continue automatically at usage limit row. Underneath, it's this key in ~/.claude/settings.json:
{
"autoContinueAtUsageLimit": true
}
It's only read from your user settings, --settings and managed settings. If none of those sets it and a project .claude/settings.json or a settings.local.json does, the feature turns off instead of the key being ignored. If one repo never resumes, look there first.
2. In Claude Desktop, tick the box. In the Code tab, the session-limit card has an Auto-continue when limits reset checkbox. With it ticked, the app retries the interrupted turn after the reset and shows the retry time on the card. It's separate from the terminal setting: turning one on doesn't turn on the other.
3. No countdown? Start it yourself. Run /rate-limit-options and pick Wait here, then continue automatically. That's the way out whenever Claude Code doesn't start waiting on its own.
When it won't resume
| Situation | What happens | What you do |
|---|---|---|
| You close the terminal or quit Claude Code | The wait is gone and doesn't come back with --resume |
Leave the session open |
| Weekly limit | If the reset is more than 24 hours away, it doesn't wait on its own. In Desktop, the weekly card has no checkbox | /rate-limit-options in the terminal, or /usage-credits |
| Your laptop sleeps for over 30 minutes and the limit resets meanwhile | The line becomes Your usage limit has reset · press enter to continue |
Press Enter when you're back |
After a shorter sleep it carries on by itself. What keeps running with the lid closed, and what doesn't, is in this other tip.
Three more things end the wait:
- You type something. Your prompt runs instead of the continuation.
- The conversation changes.
/clear,/resumeinto another session,/loginas another account, or handing the session to Desktop or the cloud. - It 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.
And one that doesn't end it but can stall it: the resumed task asks for permissions like any other turn. If it asks while you're away, it sits there until you answer. To keep it from stopping on every routine action, auto mode approves the safe ones without asking.
There's no wait in -p mode or in background sessions. Nor with an API key, a cloud provider or usage-based billing: you pay per request there, so there's no reset to wait for.
Resuming before the reset
During the wait, if you buy extra usage with /usage-credits or switch models with /model, Claude Code checks whether you have allowance again and, if you do, continues right away. On an Opus limit, switching to Sonnet lets you keep going without waiting.
What else pauses
/goal pauses at the limit and carries on at reset since v2.1.269. Dynamic workflows do the same since v2.1.271; before that they dropped the affected agents.
Official docs: Wait for a usage limit to reset · You've hit your session limit · autoContinueAtUsageLimit
Requirements
- Claude Code v2.1.234 or later, in an interactive session with a claude.ai subscription. Checked against v2.1.282 on September 28, 2026.