Stop or Delete a Workspace

Stop a workspaceCopy Anchor Link

Stopping pauses a workspace so it stops using CPU and memory. Depending on the provider, Devsy stops the container or shuts down the VM it runs on. Its data is kept.

In Devsy Desktop, open the workspace's actions menu and choose Stop. With the CLI:

devsy workspace stop my-workspace

Start it again with:

devsy workspace up my-workspace

Some providers stop idle workspaces on their own. See Auto-inactivity timeout.

Stopping or deleting a workspace first cancels any running devsy workspace up --detach task for it. To cancel a task yourself, use devsy workspace task cancel <task-id>.

Delete a workspaceCopy Anchor Link

Deleting removes the workspace and everything Devsy stores about it. Depending on the provider, that means removing a container or deleting a VM.

In Devsy Desktop, open the workspace's actions menu, choose Delete, and confirm. If the action fails, the error appears on the workspace detail page, where you can also open the logs.

With the CLI:

devsy workspace delete my-workspace

devsy workspace down and devsy workspace rm are aliases for the same command.

If the provider is unreachable, you can force the delete:

devsy workspace delete my-workspace --force

--force makes several provider teardown errors non-fatal. For container deletion (including machine providers without autoDelete), a failed container teardown is ignored, with errors other than a deadline timeout logged, and if Devsy cannot check the machine status it skips the container teardown. For auto-delete machines, a failed machine delete command is logged and the delete continues. Daemon-backed workspaces still attempt their instance delete under --force; delete request errors other than NotFound are logged and do not stop deletion, but waiting for deletion can still return an error. Provider resources may remain in these cases.