Create a workspace
Walk through the three-step Create New Workspace flow: pick a template, compose machines from recipes and stacks, then finalize.
Open Workspace List#
Sign in to the dashboard and click Workspaces -> Workspace List in the left nav. Each card on this page is one workspace - status pill on the left, kebab menu top-right, machine and stack icons across the bottom.
+N when the workspace has more than five. Hover any card on the real dashboard to see the full breakdown.Step 1 - Choose a Workspace Template#
Click + New Workspace. The wizard opens with a three-step header: Choose a Workspace Template → Add Machines → Finalize. Pick a template whose machines and stacks are close to what you need, or start with the empty template and compose your own from scratch in step 2.
Step 2 - Add Machines#
This screen shows every machine that will boot. Each machine card has the recipe icon and name in the header, the stacks attached to that machine listed underneath, and a footer with the chosen vCPU / RAM / disk. Click + Add Machine to add another, or the pencil/copy/trash icons on a card to edit, duplicate, or remove it.
The Add a Machine modal#
Clicking Add Machine opens a 3-step modal: Pick a Recipe → Add Stacks → Resources. Each step is a separate screen with its own next button.
Pick a Recipe#
The recipe is the base of the machine: which OS to boot, which packages to pre-install, which services to start. Each recipe maps to one Ansible role on the backend. Browse the catalog or use the search to filter.
Add Stacks#
Stacks layer additional tools on top of the recipe. The catalog ships with the following stacks; the Kubernetes-only ones are muted and only enabled when the recipe is a k8s cluster (k3s, kind, k8s_cluster).
Some stacks need configuration once selected: GitHub asks for a repository URL, Docker Image asks for an image list, Bash and Ansible give you an editor for the script or playbook. The form adapts based on the stack.
Resources#
Pick vCPU, RAM, and disk for this machine. Defaults come from the recipe; the maximum is capped by your account plan.
Step 3 - Finalize#
Give the workspace a name, set a Duration (the time budget after which EasyEnv automatically stops the workspace), and click Create workspace. The wizard closes and the new workspace card appears in the list with status Starting up. The blue progress bar across the top edge of the card fills as each machine boots.
After it boots#
When every machine reports active, the card flips to Running and the action row swaps from a progress bar to a Console + Stop pair. Click Console to open the workspace console (terminals, AI chat, port view) - see Workspace console for the layout.
From the CLI#
If you live in the terminal, the same operation is one command:
# Create a workspace from a template
easyenv workspace create \
--template python_devenv \
--name review-pr-1284 \
--ttl 8hSee the full flag set in the CLI workspace reference.
Troubleshooting#
- Stuck in Starting up: open the workspace audit (Audit on a failed card or the audit link from the workspace details dialog) and read the boot log. A recipe that depends on a slow apt mirror can take several minutes on first boot.
- Plan limit reached: stop or archive an unused workspace, or upgrade your plan.
- Failed status: hit
Cloneon the failed card to spin up a fresh copy with the same recipes and stacks. Inspect the original viaAuditto see what went wrong.