Vercel Sandbox Updates & Release Notes

Minor Changes

Move the interactive shell server out of the sandbox and into the sandbox-controller. sandbox connect/ssh (CLI) and the new Sandbox.openInteractive() (SDK) now request a WebSocket URL and token from the API and connect to the controller-hosted PTY, instead of installing and bootstrapping the vc-interactive-server binary inside the sandbox at connect time. This removes the bundled server binary along with the @vercel/pty-tunnel and @vercel/pty-tunnel-server packages. (#222)

Patch Changes

Upgrade Zod to v4 and update validators for Zod 4 compatibility. (#219)

Minor Changes

Move the interactive shell server out of the sandbox and into the sandbox-controller. sandbox connect/ssh (CLI) and the new Sandbox.openInteractive() (SDK) now request a WebSocket URL and token from the API and connect to the controller-hosted PTY, instead of installing and bootstrapping the vc-interactive-server binary inside the sandbox at connect time. This removes the bundled server binary along with the @vercel/pty-tunnel and @vercel/pty-tunnel-server packages. (#222)

Patch Changes

Updated dependencies [4b8970d53239f50384063ddd8690ff0091f5eaa0, b37dcabfa323a1a8a13c5479dce8c28dcdbce7f4]:

• @vercel/[email protected]

Patch Changes

Fix sandbox connect hanging or failing on a stopped/resumed sandbox. The interactive shell now surfaces attach() failures instead of swallowing them once the connection handshake lands, always stops the spinner on teardown (so a failure can no longer hang the process), and includes the in-sandbox server's stderr when the interactive server exits early. The in-sandbox vc-interactive-server also health-checks a reused server before trusting a leftover config file, so a stale /tmp/vercel/interactive/config.json restored from a snapshot no longer causes it to connect to a dead socket. (#215)

Patch Changes

• Retry the interactive shell WebSocket open on connection failure so sandbox connect recovers when the sandbox-router cache is briefly stale after a named-sandbox resume. (#210)
• Show the current snapshot's siblings in snapshots tree. The tree now reads the API's anchor node so snapshots sharing the current snapshot's parent are listed, and siblings are rendered by snapshot ID instead of source session ID. (#211)
• Updated dependencies [7a0cddea2848ad040a5281d6fd817cbc421ffc0e]:
  • @vercel/[email protected]

Major Changes

Introduce named and long-lived sandboxes (#177)

Minor Changes

Add L7 request matchers and forward URLs support to network policy rules. (#177)

Support pagination (CLI and SDK) when listing sandboxes, snapshots, sessions (#177)

Add defineSandboxProxy helper in @vercel/sandbox/proxy to easily implement network policies forwarding rules (#188)

Rename sandbox to session, namedSandbox to sandbox (#177)

Support keepLastSnapshots feature for CLI and SDK (#193)

Add sandbox port replacement support through update. (#177)

Support default snapshot expiration for persistent sandboxes (#177)

Refactor the sandbox update and deprecate old network-policy update (#177)

Support a new method: Sandbox.getOrCreate() (#177)

Rename snapshotOnShutdown to persistent (#177)

Automatically scale memory to vcpu when updating (#177)

Move to cursor pagination. Support new sortyBy parameter for lists. Support new statusUpdatedAt filter (#177)

Add Sandbox.fork(...) to the SDK and sandbox fork <source> to the CLI for forking an existing sandbox into a new one. (#205)

Remove support for blocking parameter in .stop() and default to always blocking. Improve CLI output when stopping a sandbox. (#177)

Lists now unwrap the json and return the items and pagination fields directly (#177)

Support new onResume parameter in Sandbox.create and Sandbox.get (#177)

Support snapshot tree pagination (#191)

Patch Changes

Add support for tags (#177)

Fix an 422 error when trying to resume a sandbox after snapshotting (#177)

Add Node 26 support. (#177)

Add support for patch + delete v2 endpoints for named sandboxes. (#177)

Fix readFile writing the API error JSON into the destination when the file response is not an octet-stream. The SDK now rejects any non-application/octet-stream response (including 2xx with a JSON error body) instead of piping it verbatim to the caller's stream. (#202)

Fix bug where the first ssh connection hang (#177)

Support updading current-snapshot-id of an existing sandbox (#177)

Fix JsDocs, messages and double-error message bug (#177)

Minor Changes

Add Sandbox.fork(...) to the SDK and sandbox fork <source> to the CLI for forking an existing sandbox into a new one. The fork copies as many config parameters as the server exposes — resources (vcpus), timeout, networkPolicy, tags, ports, persistent, snapshotExpiration, keepLastSnapshots — and lets the caller override any of them. Environment variables are not copied (encrypted server-side) and must be re-supplied via env / --env. (#205)

Breaking: removed sandbox create --sandbox-snapshot <name> and Snapshot.fromSandbox(name). Use sandbox fork <name> / Sandbox.fork({ sourceSandbox: name }) instead. Raw snapshot IDs are still supported via sandbox create --snapshot <id> and Sandbox.create({ source: { type: "snapshot", snapshotId } }).