Runtime changelog, 30 September 2026

What shipped in Runtime Cloud on 30 September 2026: environment variables for a whole sandbox; delete a sandbox for good; switch a sandbox to a new image and keep your work; folders over plain HTTP; file changes to your webhooks; choose which sites may embed a preview; join your Tailscale network; trial sandboxes keep going while they work; commands near the end of a lease run; a failed pause keeps your files; the CLI lists everything and says why; clearer errors; console links land where they point; and a payment under review says so.

Environment variables for a whole sandbox

Pass env at create, or change it later with an update, and every command, background process, terminal, SSH session and image start command gets those variables. Values are stored encrypted and never shown back. See the API.

Delete a sandbox for good

DELETE /v1/sandboxes/{id}, sbx.delete() and runtime sandbox rm stop it, remove its disk and paused memory, revoke its previews and ports, and free its name. Usage and audit history stay.

Switch a sandbox to a new image and keep your work

Switching keeps the sandbox's id, name, /workspace, volumes, environment, previews and ports; processes restart. See images.

Folders over plain HTTP

Upload or download a whole folder of any size as a tar stream; the SDKs unpack a download as it arrives and put it in place only once it is whole.

File changes to your webhooks

A watch started with webhook: true sends sandbox.files.changed events, signed and retried like every webhook, without keeping the sandbox awake. See observability.

Choose which sites may embed a preview

embedOrigins lists them, and a private link's token is refused in any other site's frame.

Join your Tailscale network

A paid sandbox can join your tailnet with an auth key stored as a secret. See networking.

Trial sandboxes keep going while they work

A trial sandbox that is still busy when its lease ends gets its timeoutSeconds again, until the trial hours run out. See the trial.

Commands near the end of a lease run

A command with no timeout of its own gets the time the lease has left instead of being refused, and a paused sandbox is never woken for a command that could not fit.

A failed pause keeps your files

If a sandbox's memory cannot be saved, it stays paused with its disk, and its next wake starts it from that disk.

The CLI lists everything and says why

runtime sandbox ls --all lists every sandbox, sandbox get shows when and why one stopped, errors name the option you typed, and <command> help prints help.

Clearer errors

The API reference lists every error code you can meet, a trial refusal names only the limits you crossed, and paid-only features say what counts as a paid account. See troubleshooting.

Console links land where they point

Signing in from any console page brings you back to that page.

A payment under review says so

When a payment is held for review, the console says it is under review rather than disputed, and spending returns when the review clears.