Skip to main content

​
Add a workspace

zombiectl workspace add [name]
The optional positional name is a human label; if omitted, the server picks a default. There is no repo URL — workspaces are tenant-scoped containers for credentials, agents, and webhook namespaces. Repos enter the picture later, when you configure per-agent webhooks (see Quickstart). For example: 
zombiectl workspace add platform-ops
The command creates the workspace, returns its workspace_id, and persists it as the active workspace in ~/.config/zombiectl/workspaces.json.

​
List workspaces

zombiectl workspace list
Lists every workspace under your tenant that the local CLI knows about, with the active marker. 
   WORKSPACE          NAME
*  ws_01J8XV9R2M      platform-ops
   ws_01J8XVKA3M      stripe-recon
   ws_01J8XVKB7N      sentry-triage
The leading * marks the active workspace (the one set by zombiectl workspace use). Add --json for the raw { items, current_workspace_id } envelope.

​
Switch the active workspace

zombiectl workspace use <workspace-id>
Makes the workspace active for subsequent CLI commands — zombiectl install --from, zombiectl list, zombiectl status, zombiectl logs, zombiectl events, zombiectl steer, and anything else that accepts a --workspace-id flag defaults to this value when the flag is omitted. The choice is persisted to ~/.config/zombiectl/workspaces.json (current_workspace_id field), so it survives across shells and sessions. Errors out if the id isn’t in your local list — run zombiectl workspace list first to see what’s available.
The dashboard at app.usezombie.com has its own workspace switcher backed by a cookie. The CLI config and the dashboard cookie are independent — switching one does not affect the other. Useful when you want the CLI pointed at staging while the browser watches production.

​
Show the active workspace

zombiectl workspace show
Prints the active workspace’s workspace_id, name, created_at, and active marker. Pass --workspace-id <id> to inspect a specific workspace without changing the active one. Add --json for scripting. This mirrors the dashboard Settings page.

​
Delete a workspace

zombiectl workspace delete <workspace-id>
Deleting a workspace:
  • Stops accepting new events immediately.
  • Allows in-flight runs to complete.
  • Retains run history for 30 days.
This action cannot be undone. You’ll need to recreate the workspace, re-add its credentials, and re-install its agents. Webhook URLs change because each new agent gets a fresh zombie_id, so any upstream webhook configurations will need to be updated too.