Runtime changelog, 13 October 2026

What shipped in Runtime Cloud on 13 October 2026: a secret can go to only some of your sandboxes; every account page is drawn from one kit; identity tokens work in a scheduled job's run; commands run in a sandbox at its open-connection limit; a terminal or tunnel cut by its sandbox ending says so; a full house names what it is waiting for; a custom image's creates start faster; an email before your sandboxes are deleted; deleting a sandbox the host had already removed completes; the support chat shows what it is doing; a quieter free hours card; pasted secrets and plural CLI options work; and a full snapshot count names its limit.

A secret can go to only some of your sandboxes

A secret reached every sandbox of the account; it can now name the sandboxes that get it, by label or by id. runtime secrets set NAME --host api.example.com --only-label role=hub (once per selector) or --only-sandbox <id> gives it to those alone, --all-sandboxes gives it to every sandbox again, and runtime secrets scope NAME changes who gets an existing secret without its value. The API takes only (and PUT /v1/egress-secrets/{name}/sandboxes), the SDKs only and secrets.scope, and MCP the same only. A new value keeps the scope it had. Settings → Secrets sets the scope and shows which sandboxes each secret reaches, and GET /v1/egress-secrets gives each scoped secret's reaches. See secrets sandboxes never see.

Every account page is drawn from one kit

Home, Usage & billing, Sandboxes, Jobs, Secrets, Networking, Settings, Support and the rest are one column 1040px wide with the same spacing, bigger buttons, 13px text at AA contrast or better, and one Select, DatePicker and Input everywhere. Each page's loading outline is measured from the page that follows it, so nothing moves when it arrives.

Identity tokens work in a scheduled job's run

identity_token() in a job answered identity_refused (403) because the run read a token left from the sandbox's warm start. The command now gets the sandbox's current identity-token request token, as a command in the sandbox does. See identity tokens.

Commands run in a sandbox at its open-connection limit

A sandbox holding all of its open connections (a crawler, a server's keep-alives) had every command answered 503 "environment unavailable" until one closed. Its environment read now goes through, and everything else over the limit is still refused.

A terminal or tunnel cut by its sandbox ending says so

When a sandbox's stop, pause, time limit or delete closes a terminal or a tunnel, you now get that reason, not 503 guest_failed.

A full house names what it is waiting for

A create from a snapshot, image or volume starts only on the servers that keep it. When those are full it answers no_capacity (409) saying so, with details.keptOn set to snapshot, image or volume, instead of saying the whole region is full; create without it to start anywhere in the region.

A custom image's creates start faster

A create from a custom image goes first to a host that already ran the image at the same vCPU, memory and disk, where it restores from a start template instead of booting cold.

An email before your sandboxes are deleted

Every account's owners are emailed the day-before deletion warning (it was sent only to pilots), with how many sandboxes and other items go and when, and a sandbox is told its retention started once, not again beside the warning. On an account without credit, adding credit before the deadline keeps them.

Deleting a sandbox the host had already removed completes

A delete the host had carried out is answered as done, no longer "Guest not found" for good.

The support chat shows what it is doing

Until the answer arrives, the chat says "Searching the docs…" and the like instead of bare dots. Account → Support is one chat window, and a short conversation lets the page scroll.

A quieter free hours card

The card on Usage & billing is small: it says the hours are included every month for paying accounts, shows one plain line once they are used, and is never red.

Pasted secrets and plural CLI options work

runtime secrets set drops the line breaks, bracketed-paste markers and outer spaces a pasted token carries, from standard input and the hidden prompt alike. --hosts a,b is --host a --host b, and likewise for --allow, --deny and --connect; any other plural is still refused as a typo.

A full snapshot count names its limit

A snapshot refused at the account's count says which limit it is and that every key's snapshots count. See limits.