Auto-Continue When Your Claude Code Session Hits the Usage Limit: The Setting That Saves Overnight Runs

Claude Code v2.1.234 added auto-continue at usage-limit reset — on by default. Background sessions no longer stall when they hit the plan cap; the interrupted turn picks up automatically once the limit resets.

If you've run a long background task — a multi-file refactor, a large test suite, an overnight codebase migration — and come back to find it frozen at a limit card, this is the fix. The feature shipped in v2.1.234 and is on by default. No config required to get it; one setting to turn it off if you want a hard stop.

How it works:

When Claude Code hits a claude.ai plan limit, the desktop app's Code tab shows a limit card with an "Auto-continue when limits reset" checkbox (pre-checked) and an "Auto-resuming at HH:MM" countdown. When the limit resets, the interrupted turn resumes automatically.

To configure it:

/config  →  "Continue automatically at usage limit"  →  toggle off

Setting it off gives you the previous behavior: hard stop, you manually resume.

The limit you need to know:

Auto-continue resumes the interrupted turn — the exact turn that was cut off, using the same context window that was active when the limit hit. If your task requires fresh state after a multi-hour wait (CI results that changed, a file that was edited by another process, a dependency that updated), the resumed turn won't see those changes. Review the resumed output before accepting it; silent wrong-direction completions are the risk, not an error.

When to leave it on: overnight or unattended agentic sessions where you want maximum continuity. When to turn it off: sessions doing write-sensitive operations where you want a review checkpoint before any further changes run.

Sources: Week 33 · August 10–14, 2026 — Claude Code Docs · Claude Code Auto-Continue at Usage Limits: On by Default in 2.1.234 — AI Catchup · Claude Code Auto-Resume at Usage Limit Reset — Get Claude Skills