Continue after the limit resets

A subscription limit stops an agent mid-task. With Continue after the limit resets on, detachbox types "continue" into its terminal the minute the limit resets, and you come back to finished work instead of a stalled prompt.

Turn it on

Open the project on Projects.
Pick Edit on the default launch, or Edit in the ⋯ menu of a saved one.
Tick Continue after the limit resets and pick Save.

The switch shows on every launch that runs on a subscription or key connected in the dashboard. Each launch has its own setting, so one agent can continue at the reset while the one next to it rotates to another subscription.

How it works

The server sees the limit line in the terminal and plans the resume for the reset time of the account the terminal runs on, plus up to 30 seconds.
At that time it reads the limits again. If the limit has not reset yet, it waits for the new reset time.
Where the agent has its own way to take a message, detachbox sends the prompt through it, so a line you are typing stays intact: Claude Code takes it as a new turn, Codex from its queue. OpenCode gets it typed in.
Codex restarts with codex resume --last first, so it picks up the fresh login.

It works for Claude Code, Codex and OpenCode. Claude Code also has its own "Continue automatically at usage limit" setting; when Claude continues by itself, detachbox stays out of its way.

When detachbox leaves a terminal alone

Someone typed into the terminal after it stopped: the planned "continue" is dropped, since you took over.
Someone typed into it in the last minute when the time comes.
The terminal waits on a menu or a question: only you answer those.
A shell terminal has no launch behind it, so nothing continues in it.

See when it resumes

The Terminals list shows a stopped terminal with the time it resumes, such as resumes 03:10. Turn on the Resumed ping in Notifications to hear about it, and Activity records each time an agent carried on after its limit reset.

Together with rotation and a reserve

With rotation on, the agent moves to another account with room left instead of waiting. It waits only when the whole pool runs out: for the earliest reset in the pool, and continues there.
An account that reached your reserve comes back after its window resets, and the terminals on it continue. Lift the reserve until the reset, and they continue at once.

What it needs

A launch on a subscription or key connected in the dashboard. A launch whose agent signs in inside the terminal has no connected account to watch, so its form leaves the switch out.