Skip to main content
Workspaces are isolated cloud environments with persistent file storage and a sandboxed execution environment for running code.

What is a workspace?

A workspace is:
  • A persistent volume for storing files (code, data, documents)
  • A sandbox environment where you can run bash commands, execute scripts, and start services
  • The unit an agent works in - point a run at a workspace and it can read, write, and execute there
  • Scoped to a user (personal workspace) or an organization (shared workspace)

Creating a workspace

Personal workspace

Organization workspace

POST /api/workspaces requires a user principal, so a service-account key gets 403. Create the workspace under an organization instead - that route accepts both. See Unattended runs.
Pass storage_region at creation to choose where the workspace’s files live: wnam, enam, weur, eeur, apac, or oc. It cannot be changed afterwards.

Listing workspaces

Updating a workspace

Who can see it

Visibility applies to organization workspaces; a personal workspace cannot change it. Managing a workspace this way needs manage access to that specific workspace, not just an organization role.

Deleting a workspace

Deleting a workspace permanently removes all files. This cannot be undone.

Running commands

Execute bash commands in the workspace sandbox. The workspace files are mounted at /ws in the sandbox, which is also the working directory.
Response:
status is completed or failed - a non-zero exit is failed, not an HTTP error. See Tools for the rest of the sandbox surface, including named sandboxes and the 10-minute command limit.