Devsy
Developing in a Workspace

Stop or Delete a Workspace

Stop a workspace

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 workspace

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

This only removes the workspace on the Devsy side and ignores provider errors, so it can leave cloud resources behind.

On this page