Auto-Inactivity Timeout
Providers can stop workspaces that nobody is using, which saves cost. A machine stopped this way keeps its data, and Devsy restarts it when you start the workspace again.
Configure the timeout
Each provider has an INACTIVITY_TIMEOUT option, for example 30m. See Set provider options. The provider's options show its default.
How it works
Non-machine providers such as Docker, Podman, Kubernetes, and Microsandbox run a process in the container that tracks activity. When nobody has connected for the timeout, it ends the container's main process. The container stops, its state is kept, and Devsy restarts it later.
Apple provider
The Apple provider deletes the container instead of stopping it. Only data on mounted volumes survives.
Machine providers run a Devsy daemon on the VM. When there is no activity for the timeout, the daemon shuts the machine down or deletes it, whichever costs less for that cloud. Devsy restarts or recreates it when you resume.
See the agent guide for how providers implement this, and Machine diagnostics for debugging.