[EhabY]

Extension side of workspace lifecycle actions in the Workspaces panel: Start, Stop, Restart, Update, Delete and Share for listed workspaces. The UI is in #1184.

• WorkspaceActionRunner runs each action over the REST API, with no CLI. It asks first where it must, re-reads the workspace, and explains when the action no longer applies. Each action gets an AbortSignal that aborts when the session changes; the signal is checked before every request and also ends any wait, because the API client is shared across sessions. Commands only gains the dashboard sharing path.
• Every action goes through one runBuild helper that queues the build with the vscode_connection reason, waits for it as coder does, streams its logs to the Coder output, warns when no provisioner can take it, and fails the action with its workspace named. When the request carries on_success, it also waits for the start the server queues after the stop.
• waitForBuild polls /api/v2/workspacebuilds/{id}, as coder delete does. The by-name read 404s once a delete completes, so a Delete always reported failure. It polls through up to 3 network failures or 5xx responses in a row and fails at once on a client error. The action returns once its build settles, without waiting for a stalled log stream.
• Start matches coder start: it activates a dormant workspace, cleans up a failed start, and uses the active version when the workspace auto-updates or the template requires it.
• Restart starts on the build's template version, and refuses to start if another build replaced its stop.
• Update asks for any parameters the new template version adds, then re-reads the workspace and refuses if start versus restart or the template version changed; telemetry records the refusal as aborted. The connected workspace still updates through a reload; the re-check covers it too, which is the one user-visible change. On Coder 2.36+ it updates in one build. Before 2.36, the panel restarts a running workspace itself, while the connected window keeps coder update.
• workspaceActions (shared) decides which actions a workspace allows. The store tracks pending actions per workspace, so actions on different workspaces run in parallel. When an action ends, the store re-reads just that workspace (the All and Shared filters don't poll), after any list already in flight, so a stale list can't undo it.
• Extension tests fake node:timers/promises through vitest's fakeNodeBuiltins.

Not covered

• Activating a dormant workspace with OAuth fails on servers that enforce scopes, because no token scope covers dormant workspaces (Scoped tokens can't read or activate dormant workspaces coder#32192). The scope suite lists updateWorkspaceDormancy as unprobed until the server fixes this.

Generated by Coder Agents for @EhabY.

[linear-code]

VSC-1

VSC-45