Vercel Sandbox Updates & Release Notes

Minor Changes

Add multi-region support: (#301)

New region and failoverRegions options on sandbox create, fork, and update (SDK), with matching flags on sandbox create, fork, run, sh, and the sandbox config region / sandbox config failover-regions commands (CLI).

New failoverRegions getter on Sandbox and regions getter on Snapshot.

Regions are now shown in sandbox ls, sessions list, snapshots list/get, sandbox config list, and the create/fork summary.

Sandbox.region and Sandbox.failoverRegions no longer return undefined: the getters now report the platform defaults (iad1 and []) when the API omits the fields, so their types are string and string[]. The new DEFAULT_SANDBOX_REGION export makes the default region readable. (#301)

Patch Changes

Updated dependencies [2997ecc32a77c145289fbbd89ae2dc0214767ae3, 2997ecc32a77c145289fbbd89ae2dc0214767ae3, 2023195eafe3199c2372f7dad8bfaf0878267c52]:

@vercel/[email protected]

Minor Changes

Add multi-region support: (#301)

New region and failoverRegions options on sandbox create, fork, and update (SDK), with matching flags on sandbox create, fork, run, sh, and the sandbox config region / sandbox config failover-regions commands (CLI).

New failoverRegions getter on Sandbox and regions getter on Snapshot.

Regions are now shown in sandbox ls, sessions list, snapshots list/get, sandbox config list, and the create/fork summary.

Sandbox.region and Sandbox.failoverRegions no longer return undefined: the getters now report the platform defaults (iad1 and []) when the API omits the fields, so their types are string and string[]. The new DEFAULT_SANDBOX_REGION export makes the default region readable. (#301)

Patch Changes

Add mock for the Drive class. (#307)

Updated dependencies [c2b5d7b45340b485264abb82f0cd640ed4e93293, 2997ecc32a77c145289fbbd89ae2dc0214767ae3, 2997ecc32a77c145289fbbd89ae2dc0214767ae3, 2023195eafe3199c2372f7dad8bfaf0878267c52]:

@vercel/[email protected]

Minor Changes

• Add multi-region support: (#301)
• New region and failoverRegions options on sandbox create, fork, and update (SDK), with matching flags on sandbox create, fork, run, sh, and the sandbox config region / sandbox config failover-regions commands (CLI).
• New failoverRegions getter on Sandbox and regions getter on Snapshot.
• Regions are now shown in sandbox ls, sessions list, snapshots list/get, sandbox config list, and the create/fork summary.
• Sandbox.region and Sandbox.failoverRegions no longer return undefined: the getters now report the platform defaults (iad1 and []) when the API omits the fields, so their types are string and string[]. The new DEFAULT_SANDBOX_REGION export makes the default region readable. (#301)

Patch Changes

• Update defineSandboxProxy to limit the JWKS issuer cache size to prevent unbounded memory usage. (#309)

Minor Changes

Add multi-region support for drives: (#307)

Set the region field when creating a new drive, or use the --region flag in the CLI.

You can retrieve the region of a drive using the region getter on the Drive class.

Drives can be only be mounted to sandboxes running on the same region.

Add multi-region support: (#301)

New region and failoverRegions options on sandbox create, fork, and update (SDK), with matching flags on sandbox create, fork, run, sh, and the sandbox config region / sandbox config failover-regions commands (CLI).

New failoverRegions getter on Sandbox and regions getter on Snapshot.

Regions are now shown in sandbox ls, sessions list, snapshots list/get, sandbox config list, and the create/fork summary.

Sandbox.region and Sandbox.failoverRegions no longer return undefined: the getters now report the platform defaults (iad1 and []) when the API omits the fields, so their types are string and string[]. The new DEFAULT_SANDBOX_REGION export makes the default region readable. (#301)

Patch Changes

Update defineSandboxProxy to limit the JWKS issuer cache size to prevent unbounded memory usage. (#309)

Minor Changes

• Add multi-region support: (#301)
• New region and failoverRegions options on sandbox create, fork, and update (SDK), with matching flags on sandbox create, fork, run, sh, and the sandbox config region / sandbox config failover-regions commands (CLI).
• New failoverRegions getter on Sandbox and regions getter on Snapshot.
• Regions are now shown in sandbox ls, sessions list, snapshots list/get, sandbox config list, and the create/fork summary.

Patch Changes

• Accept none for --failover-regions on sandbox create, sandbox run and sandbox fork. (#310)

sandbox config failover-regions <name> none already clears the list, but at creation time
none was forwarded as a literal region name and rejected by the API. With a project-level
default failover list there was no way to create a sandbox in one of those regions from the
CLI, while the SDK and the HTTP API both accept an empty failoverRegions array.

The none sentinel is now shared between create/run/fork and config.

• Sandbox.region and Sandbox.failoverRegions no longer return undefined: the getters now report the platform defaults (iad1 and []) when the API omits the fields, so their types are string and string[]. The new DEFAULT_SANDBOX_REGION export makes the default region readable. (#301)

Updated dependencies [2997ecc32a77c145289fbbd89ae2dc0214767ae3, 2997ecc32a77c145289fbbd89ae2dc0214767ae3, 2023195eafe3199c2372f7dad8bfaf0878267c52]:
@vercel/[email protected]

Minor Changes

Add multi-region support for drives: (#307)

Set the region field when creating a new drive, or use the --region flag in the CLI.

You can retrieve the region of a drive using the region getter on the Drive class.

Drives can be only be mounted to sandboxes running on the same region.

Add multi-region support: (#301)

New region and failoverRegions options on sandbox create, fork, and update (SDK), with matching flags on sandbox create, fork, run, sh, and the sandbox config region / sandbox config failover-regions commands (CLI).

New failoverRegions getter on Sandbox and regions getter on Snapshot.

Regions are now shown in sandbox ls, sessions list, snapshots list/get, sandbox config list, and the create/fork summary.

Patch Changes

Sandbox.region and Sandbox.failoverRegions no longer return undefined: the getters now report the platform defaults (iad1 and []) when the API omits the fields, so their types are string and string[]. The new DEFAULT_SANDBOX_REGION export makes the default region readable. (#301)

Updated dependencies [c2b5d7b45340b485264abb82f0cd640ed4e93293, 2997ecc32a77c145289fbbd89ae2dc0214767ae3, 2997ecc32a77c145289fbbd89ae2dc0214767ae3, 2023195eafe3199c2372f7dad8bfaf0878267c52]:

@vercel/[email protected]

Patch Changes

Surface the server's error message in APIError.message. Failed API requests previously reported only Status code 400 is not ok, hiding the actionable detail (e.g. Invalid request: ports should NOT have more than 15 items.) in error.json. The message now includes it directly. (#291)

Correct the ports option JSDoc: the limit is 15 ports (matching the docs and API validation), not 4. (#292)

Correct the resume option JSDoc on Sandbox.get and Sandbox.getOrCreate: the default is false (the client omits the param and the API defaults to not resuming), not true. A stopped persistent sandbox still auto-resumes on the first SDK call that needs a running session. (#293)

Patch Changes

• Sandbox-lookup 404 errors are now quiet and actionable: the error states the name was not found, the status code, and a closing hint to run sandbox ls --all. The request URL and response-buffer path move behind DEBUG=sandbox:errors. (#298)
• create and fork output now ends with a connect hint (connect with: sandbox ssh <name>), so a fresh sandbox never leaves you without a next step. Composing commands like run suppress it. (#296)
• sandbox sh <command> now explains that sh takes no command and points at sandbox run -i <command>. (#299)
• create, sh, and run check for a newer published CLI and print an update notice when the install is behind. The result is cached to a file and refreshed at most once per hour; when a lookup does run it happens concurrently with sandbox creation and is aborted as the command finishes, so it never adds latency or delays exit. Disable with SANDBOX_SKIP_VERSION_CHECK=1. (#297)
• Updated dependencies [0d3b1aa410454b20562ea010cd66611a9a477b2d, bd4110aa6231a2e845630cc02e9d69cb02fb28ad, 2c2c942239fd9ef47bed0b9295389b702ce6c0ff]:
  • @vercel/[email protected]

Major Changes

Add support for Vercel Managed Images and deprecate the runtime option in the SDK and CLI. Runtime-based creation remains supported through the legacy v2 API; image-based and default creation use the v3 API. Passing both runtime and image is an error. (#276)

Sandboxes that do not specify an image now use vercel/sandbox/universal. The previous default was the node24 runtime on Amazon Linux 2023. The new default is based on Ubuntu and includes Node.js 24, Bun, Python 3.14, coding agents, and common development and debugging tools.

Existing runtime calls continue to work, it's recommended to migrate to Vercel managed images when possible:

• Not using runtime: omit image to use the new Universal image, or set image: "vercel/sandbox/node:24" for an Ubuntu-based Node.js equivalent to the previous default.
• Using runtime: "node22": use image: "vercel/sandbox/node:22" for an Ubuntu-based equivalent.
• Using runtime: "node24": use image: "vercel/sandbox/node:24" for an Ubuntu-based equivalent.
• Using runtime: "node26": use image: "vercel/sandbox/node:26" for an Ubuntu-based equivalent.
• Using runtime: "python3.13": use image: "vercel/sandbox/python:3.14" for an Ubuntu-based equivalent, and note the Python version upgrade.

Patch Changes

Updated dependencies [5c9e2d5f34f20632ed5a1de1288e811b67b95423]:

• @vercel/[email protected]

Major Changes

Add support for Vercel Managed Images and deprecate the runtime option in the SDK and CLI. Runtime-based creation remains supported through the legacy v2 API; image-based and default creation use the v3 API. Passing both runtime and image is an error. (#276)

Sandboxes that do not specify an image now use vercel/sandbox/universal. The previous default was the node24 runtime on Amazon Linux 2023. The new default is based on Ubuntu and includes Node.js 24, Bun, Python 3.14, coding agents, and common development and debugging tools.

Existing runtime calls continue to work, it's recommended to migrate to Vercel managed images when possible:

• Not using runtime: omit image to use the new Universal image, or set image: "vercel/sandbox/node:24" for an Ubuntu-based Node.js equivalent to the previous default.
• Using runtime: "node22": use image: "vercel/sandbox/node:22" for an Ubuntu-based equivalent.
• Using runtime: "node24": use image: "vercel/sandbox/node:24" for an Ubuntu-based equivalent.
• Using runtime: "node26": use image: "vercel/sandbox/node:26" for an Ubuntu-based equivalent.
• Using runtime: "python3.13": use image: "vercel/sandbox/python:3.14" for an Ubuntu-based equivalent, and note the Python version upgrade.

Major Changes

Add support for Vercel Managed Images and deprecate the runtime option in the SDK and CLI. Runtime-based creation remains supported through the legacy v2 API; image-based and default creation use the v3 API. Passing both runtime and image is an error. (#276)

Sandboxes that do not specify an image now use vercel/sandbox/universal. The previous default was the node24 runtime on Amazon Linux 2023. The new default is based on Ubuntu and includes Node.js 24, Bun, Python 3.14, coding agents, and common development and debugging tools.

Existing runtime calls continue to work, it's recommended to migrate to Vercel managed images when possible:

• Not using runtime: omit image to use the new Universal image, or set image: "vercel/sandbox/node:24" for an Ubuntu-based Node.js equivalent to the previous default.
• Using runtime: "node22": use image: "vercel/sandbox/node:22" for an Ubuntu-based equivalent.
• Using runtime: "node24": use image: "vercel/sandbox/node:24" for an Ubuntu-based equivalent.
• Using runtime: "node26": use image: "vercel/sandbox/node:26" for an Ubuntu-based equivalent.
• Using runtime: "python3.13": use image: "vercel/sandbox/python:3.14" for an Ubuntu-based equivalent, and note the Python version upgrade.

Patch Changes

Use the invoked app name in help examples so vercel sandbox --help shows vercel sandbox ... commands instead of the standalone sandbox ... form, which is not on PATH for Vercel CLI users. (#269)

Updated dependencies [5c9e2d5f34f20632ed5a1de1288e811b67b95423]:

• @vercel/[email protected]