Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublic
Assigneeszack

Relationships

#4849 Workspace requests on the root: serve handles workspace.*

Opened by zack · 11/17/2026· Shipped 11/18/2026

Issue 11 of the execution plan in design/surfaces/serve-workspaces.md. One PR. Depends on swamp-club#4848 (workspace services).

Problem

The workspace services run only in a process that can see the host folder. A person or a CI job on another machine has no way to create, list, suspend or delete a workspace.

The root workspace is the serve that takes these requests. Its grants decide who may make them and its audit log records each one.

Change

  • The host tells the root where the workspaces are. When the host starts the root it gives it the workspaces/ folder and the host's address. The PR chooses how, a hidden flag or the child's environment. Only the root is given them.
  • Serve handles workspace.*. workspace.create, workspace.list, workspace.get, workspace.suspend, workspace.resume and workspace.delete: protocol types, request schemas, and a place for each in the follower lists, which say what a follower node does with a request type.
  • create never starts a serve. The workspace is made and listed as suspended. workspace.resume starts it.
  • A serve that is not a host's root refuses them. A serve started without the folder answers every workspace.* request with an error that says so.
  • Authorization. The root's admins may make every request. Any authenticated principal may list. The workspace kind in grants is the next step in the plan.
  • Audit. Each request is recorded in the root's audit log with the caller and the workspace name, refused requests included.
  • A token-mode root refuses create. Until the sign-in exchange exists, the creator of a workspace under a token-mode root would have no way to get a token inside it. The error says that. The sign-in exchange issue lifts the refusal.

The creator recorded in the wanted file, and the first admin written to the workspace's serve.yaml, are the caller.

Done when

  • A root admin can create, list, get, suspend, resume and delete a workspace against a temp host folder.
  • A principal who is not a root admin can list and is refused everything else.
  • A serve with no workspaces folder refuses each request.
  • A token-mode root refuses create and names the reason.
  • create leaves a workspace that is listed as suspended, and resume starts it.
  • Each request, allowed or refused, appears in the audit log.
  • Tests run in-process. A test that authenticates through serve's HTTP routes as a fixed principal calls resetRateLimitState() first.

Out of scope

  • The swamp serve workspace commands. The next issue in the plan.
  • The workspace kind in grants.
  • The sign-in exchange.
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 8 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

11/18/2026, 6:08:59 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
zack assigned zack11/18/2026, 5:06:49 PM

Sign in to post a ripple.