Edit a workspace

Rename a workspace, change its Duration, or add and remove machines. Editing the shape (machines + stacks) is only available before boot - a Running workspace is locked at the shape it booted with.

Change name or Duration#

Click the workspace card's kebab menu and pick Edit. The Edit option is only enabled when the workspace status is Not started - once the workspace boots, its name and Duration are locked. Use Clone if you need a fresh copy with different metadata.

Open Edit
Three-dot menu on a Not-started card → Edit.
Update fields
Change the name, Duration, or visibility. Hit Save changes.
Boot when ready
Hit Start on the card to boot with the new values.

dashboard.easyenv.io/dashboard/acme-engineering/workspaces/review-pr-1284

EEasyEnv

acme-engineering

Team plan

John Doe

review-pr-1284

Edit workspace

Save changes

Namereview-pr-1284Duration8 hoursDescriptionRepro for issue #1284Optional. Visible to members.VisibilityAccount members only

The Edit dialog. Available on Not-started workspaces only - Running workspaces are locked at the shape they booted with.

Edit machines#

While the workspace is Not started, the Edit dialog also surfaces every machine card with the same pencil / copy / trash actions as the create wizard. You can swap a recipe, change which stacks are attached, resize CPU/RAM/disk, or duplicate a machine.

Add or remove machines#

A running workspace can grow or shrink. To add a machine, click + Add machine on the workspace page and pick a recipe. The new machine is provisioned in place and joins the same private network as the existing machines.

To remove a machine, open Edit while the workspace is Not started and use the trash icon on the machine card. To remove a machine from a Running workspace you have to Clone the workspace, drop the machine in the new copy's Edit step, and boot the clone.

Side effects of removing a machine

Other machines that point at the removed host (e.g. an app server with a Postgres connection string) will start failing as soon as you boot. Update configs in the same Edit pass.

Restart a machine#

Reboots are common during interviews when a candidate breaks the environment. Inside the workspace console, the machine row in the left rail has a Restart action; the VM reboots in place and the disk and home directory are preserved.

From the CLI:

bash

easyenv machine restart <machine-id>

Edit files inside a machine#

You have three ways to change files on a machine:

Browser terminal: the center pane of the console is one xterm.js shell per machine. Use any TUI editor - vim, nano, or helix are installed by default on most recipes.
Browser VS Code: when a machine has the VS Code stack, the console's port view button opens code-server in a new tab - the full VS Code UI, in your browser.
Claude Code in the terminal: when a machine has the Claude stack, run claude inside the terminal to launch the CLI on the same machine.

What you cannot edit#

A small set of attributes are immutable after the workspace boots:

Machines and stacks: the machine list, the stacks attached to each machine, and the per-machine resources are locked once the workspace status leaves Not started. Use Clone to spin up a new copy with a different shape.
Account ownership: a workspace cannot be moved between accounts.