Sandboxes
A sandbox is a long-running container inside a project, useful for development shells, one-off jobs and small internal services. Create one from Sandboxes → Create Sandbox.
A sandbox belongs to a project: projectId is required on create. A request without one is refused with 400 validation_error ("projectId is required. Services live inside a project — create or pick a project first.") rather than being provisioned as an org-scoped container.
Base toolchain
Every sandbox is provisioned with a usable toolchain so it works the moment it starts:
apt-get update && apt-get install -y \
nano curl git wget unzip ca-certificates gnupg \
procps iputils-ping build-essentialAlpine images get the equivalent apk packages. Install failures are swallowed so a flaky mirror cannot wedge the container; you can always install more later.
Web terminal
Each sandbox hosts a browser terminal and, for supported images, a VS Code server. Open it from the sandbox list — the connection is authenticated with the same session as the console.
The terminal is a WebSocket at /api/v1/sandboxes/:id/terminal, and the same shell is reachable for a deployed app service at /api/v1/apps/:projectId/:serviceName/terminal (the endpoint a dashboard "Terminal" tab connects to). Both authenticate from the session cookie, so they are for people and browser clients: an API key is not accepted, and there is no REST endpoint that runs a command and returns its output. A machine that needs to execute inside a sandbox should drive the socket with the session cookie, or ask a person to.
Either socket reports why it refused — as a red line in the terminal followed by a close code (4401 sign-in, 4403 role, 4404 gone, 4409 not running) — so a failure never renders as a blinking cursor.
Lifecycle
Sandboxes can be stopped and restarted without losing their volume. Restarting re-runs the provisioning step, so a toolchain change made since the last start takes effect on the next start, not on a running container.
Resources
CPU, memory and storage are set at creation. A sandbox is a container, not a virtual machine: treat it as ephemeral compute with a persistent volume.