Daily Work

Manage workspaces

Use My Workspaces to start, stop, update, launch, inspect, and delete workspaces without leaving Console.

Customer adminsCustomer membersPlatform operators
Console-rendered My Workspaces grid with safe running, stopped, and attention states plus launch actions.
Console-rendered example with safe data: stopped workspaces stay visible so users can restart, update, launch, or delete from the same grid.

Read workspace status

My Workspaces shows running, stopped, starting, updating, failed, and attention states. Stopped workspaces remain visible so they can be restarted, updated, inspected, or deleted.

StatusMeaningCommon action
RunningRuntime is active.Launch Browser IDE or stop when done.
StoppedRuntime is not active.Start before working or delete if no longer needed.
Starting or updatingA build is active.Wait for the build result.
Failed or attentionBuild or runtime needs review.Open logs or ask support before deleting storage.

Start a stopped workspace

  1. Open My Workspaces.
  2. Find the stopped workspace.
  3. Click Start.
  4. Wait for status to become ready or running.
  5. Launch Browser IDE.

Starting does not recreate the workspace from scratch. It brings the existing workspace runtime back online.

Stop a running workspace

  1. Open My Workspaces.
  2. Find the running workspace.
  3. Click Stop.
  4. Confirm the status changes to stopped.

Stopping helps control runtime usage. It is different from delete. Storage and workspace records remain available according to the platform policy.

Update safely

  1. Click Update or Review update.
  2. Read the planned template and parameter changes.
  3. Confirm credential refresh status.
  4. Check that secret values remain hidden.
  5. Click Run update only when the plan is correct.

Update should show non-secret parameter changes before a build starts. If a field fails validation, fix it in the review instead of starting the build repeatedly.

Delete a workspace

Delete only when you intentionally want the managed workspace removed. Use the Console delete action so cleanup can follow the supported path.

Do not manually delete PVCs, pods, Kubernetes Secrets, or Coder objects for a normal customer delete. If cleanup appears stuck, include the workspace name, status, and last action in the support handoff.

Editor launch options

ActionUse when
Browser IDEYou want the default in-browser editor.
VS Code DesktopYour local VS Code is configured for this workspace flow.
JetBrainsYour team uses JetBrains remote workflows.
SSH ConfigYou need an advanced terminal or editor connection.

Browser IDE is the default path for most customer users.

Done When

  • The workspace row shows the expected status.
  • Start is available for stopped workspaces.
  • Stop is available for running or starting workspaces.
  • Update review finishes before a build starts.
  • Delete confirmation matches the workspace you intend to remove.