Claude Code can now resume itself after a limit reset

Claude Code's desktop client has gained an auto-continue checkbox that restarts a paused session at the point where a usage limit stopped it. The change was announced by the Claude Code team on X, which described the option as continuing the work automatically once the limit resets.

At a glance

• The option sits behind a single checkbox in the desktop client, and leaving it ticked hands the resumption to Claude Code itself rather than to a session picked up by hand after the wait.
• Sessions stop when the subscription usage limit is reached, and Claude Code prints a notice carrying the time of the next reset, the same moment the new option now waits for.
• Anthropic's documentation does not describe the checkbox, and the GitHub issue asking for the behaviour, numbered #35744, was still listed as open as of 13 August, despite the option appearing in the client.

Why it matters Usage limits are the main friction point in long Claude Code runs, and the cost of hitting one is not only the wait but the work of rebuilding a session by hand afterwards. An automatic resume appears to target that second cost rather than the limits themselves, which are unchanged. It also reads as an acknowledgement that the reset clock, not the model, sets the rhythm of a working day for subscription users.

Claude Code pauses when a session runs into the usage limit attached to the subscription, and the client surfaces a message stating that the limit has been reached along with the time at which it resets. The auto-continue option builds on that reset time: with the box ticked, the session picks up where it stopped.

Usage limit behaviour is not uniform across plans. According to Anthropic's documentation, Enterprise seats operating under rolling window limits and API key users on pay-as-you-go billing have different usage limit behaviour from standard subscription limits. The checkbox itself was announced for the desktop client.

The feature also has a public paper trail. A request for this behaviour was filed on GitHub as issue #35744, and it was still listed as open as of 13 August, while Anthropic's documentation carries no description of the new checkbox at all.

What's next The open questions cluster around scope: whether the option extends past the desktop client, and how it behaves in the Enterprise and API cases where limits are handled differently. The number of consecutive resets a single session can ride through is also unstated, as is any timeline for documenting the setting. Issue #35744 remains the public tracker for the original request.