CapabilitiesIdle and waking
Choose the idle timeout
You set how long an idle machine waits before it pauses or stops, including never.
Who offers it
Part of Idle timers, waking and session limits, which explains why it matters.
Fully: Agent 37, boxd, Daytona, Runtime, Sandboxer and Tensorlake. With a catch: Boat, Cloudflare Sandbox, E2B, InstaBox, Modal and Morph. Not at all: Blaxel, Lizard, Sprites and Vercel Sandbox.
The range is the auto-sleep setting; 0 or off means it never sleeps.
docs-confirmed “Once no bytes have moved through any of its URLs for `idle_timeout_seconds` (default 900, from five minutes to a day)” Source
The timer counts network traffic, so a machine working offline looks idle.
docs-confirmed “boxd machine config set myapp auto-hibernate.timeout 0 # never hibernate this machine” Source
Separate settings exist for stop, pause, archive and delete.
docs-confirmed “The auto-stop interval sets the amount of time after which a running sandbox is automatically stopped.” Source
The default is five minutes; `persistent: true` turns the idle pause off.
docs-confirmed “A sandbox pauses itself after **300 seconds** of idle time.” Source
The default depends on the plan; 0 means never pause.
docs-confirmed “`sbx idle sb_k3v9x2mq 0` # never pause this one” Source
- TensorlakeYes
The value is an idle threshold; 0 asks for the plan maximum.
docs-confirmed “`timeout_secs` is an **idle threshold**, not a wall-clock lifetime.” Source
The catch: The clock counts from when the machine started, not from when it was last used, so a busy machine is stopped too.
docs-confirmed “Each resume sets the deadline again.” Source
The catch: You can set the wait up to 6 hours, but the setting is lost when the object restarts and there is no never.
docs-confirmed “Its instance can keep running through the restart. The restarted Durable Object starts without an inactivity timeout” Source
The catch: The clock counts down from creation and commands do not reset it, and the default action is to kill rather than pause.
docs-confirmed “Every sandbox has a timeout, and it defaults to **5 minutes** if you do not set one.” Source
The catch: Only paid plans can choose; the free plan is fixed at 30 minutes and cannot turn it off.
docs-confirmed “A new machine pauses once it has been idle for 30 minutes. On a paid plan you can choose 5 to 30 minutes, or `instabox auto-suspend <machine> 0` to turn that off” Source
- ModalWith a catch
The catch: You can set an idle timeout, but reaching it ends the machine rather than pausing it.
docs-confirmed “Sandboxes can also be automatically terminated after a period of inactivity - you can do this by setting the `idle_timeout` parameter.” Source
- MorphWith a catch
The catch: You can switch the idle pause off, but the docs never say how long it waits or what values you can set.
docs-confirmed “Devboxes support wake-on-SSH/HTTP and TTL policies to auto-pause idle machines.” Source
- BlaxelNo
There is no setting for how long an idle machine waits; standby happens on its own.
docs-confirmed “There are no built-in stop or start functions available in the SDKs to manage standby mode.” Source
- LizardNo
There is no idle timer, only a lifetime deadline that a busy machine also hits.
docs-confirmed “This is not an idle timer.” Source
- SpritesNo
The idle window is about 30 seconds and there is no setting for it.
docs-confirmed “You don't choose between them and you can't see the transition.” Source
There is only a session length, not an idle timer you can set.
docs-confirmed “Max Session Duration| 45 minutes| 24 hours| 24 hours” Source
Related
Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.