Vercel Sandbox Updates & Release Notes

Minor Changes

Add response to network policy rules, so a rule can be answered by the sandbox proxy instead of being sent to the destination. A trailing response rule with no match answers whatever the earlier rules did not claim, which restricts an allowed domain to specific paths without running your own proxy. (#328)

Tag API requests with the AI agent driving the process, when one is (#320) detected via detect-agent, as an agent/<name> phrase in the user-agent header. No agent detected means no change to the header. The SDK sends no telemetry events; this is request metadata only.

Patch Changes

Resume sessions through the API when they are stopping or snapshotting instead of polling indefinitely for a terminal status. (#344)

Stabilize sandbox integration tests by isolating sandbox-list queries and cleanup, and remove an obsolete sudo PATH assertion. (#346)

Patch Changes

• Label sizes with binary units (KiB, MiB, GiB, TiB) instead of KB/MB/GB/TB. The CLI already divided by 1024, so a 1 TiB drive printed as 1 TB; drive, snapshot and network-transfer sizes now match the units used in the docs. (#341)

• sandbox fork now looks up the source before forking and warns on stderr when it is running. A fork starts from the source's latest snapshot (or a fresh copy of its runtime when it has none), never from the live filesystem, so anything written in a running source since its last snapshot is left behind while the command still exits 0. The warning points at sandbox snapshot --stop <source> as the way to fork the current state, and fork --help now says the same. (#340)

• Tag API requests with the AI agent driving the process, when one is (#320)
  detected via detect-agent, as an agent/<name> phrase in the user-agent
  header. No agent detected means no change to the header. The SDK sends no
  telemetry events; this is request metadata only.

• Updated dependencies [fdd6912470338b15e303eaf515a78c21b2b19473, 27ad49a0ccc7aa81a96a3b3c2eaf7948140ce708, 4e7ab569a7e6cd905d43a198f2e08a627457a8ea, 9d0403de39a4e58a2d37bdc1a00ca810e109e57b]:
  @vercel/[email protected]

Minor Changes

Add support for Drives, persistent storage that can store TBs of data and be mounted on sandboxes at a specific path. Drives support point-in-time, read-only snapshots. (#285)

Get started by creating a drive, then mount it on a sandbox:

import { Sandbox, Drive } from "@vercel/sandbox";
const drive = await Drive.getOrCreate({ name: "workspace-cache" });
// Mount as read-write once
const sandbox = await Sandbox.create({
name: "my-sandbox",
mounts: {
"/data": drive,
},
});

Create a snapshot to mount the same drive on multiple sandboxes at a time:

import { Sandbox, Drive } from "@vercel/sandbox";
const drive = await Drive.getOrCreate({ name: "shared" });
// Mount many snapshots of the same drive
const firstReader = await Sandbox.create({
name: "reader-1",
mounts: {
"/data": drive.snapshot(),
},
});
const secondReader = await Sandbox.create({
name: "reader-2",
mounts: {
"/data": drive.snapshot(),
},
});

Read the documentation to learn more: https://vercel.com/docs/sandbox/concepts/drives

Patch Changes

Updated dependencies [6afca1fe55c9058416b622d1108123134bc5ff5e]:
@vercel/[email protected]

Minor Changes

Add support for Drives, persistent storage that can store TBs of data and be mounted on sandboxes at a specific path. Drives support point-in-time, read-only snapshots. (#285)

Get started by creating a drive, then mount it on a sandbox:

import { Sandbox, Drive } from "@vercel/sandbox";
const drive = await Drive.getOrCreate({ name: "workspace-cache" });
// Mount as read-write once
const sandbox = await Sandbox.create({
name: "my-sandbox",
mounts: {
"/data": drive,
},
});

Create a snapshot to mount the same drive on multiple sandboxes at a time:

import { Sandbox, Drive } from "@vercel/sandbox";
const drive = await Drive.getOrCreate({ name: "shared" });
// Mount many snapshots of the same drive
const firstReader = await Sandbox.create({
name: "reader-1",
mounts: {
"/data": drive.snapshot(),
},
});
const secondReader = await Sandbox.create({
name: "reader-2",
mounts: {
"/data": drive.snapshot(),
},
});

Read the documentation to learn more: https://vercel.com/docs/sandbox/concepts/drives

Minor Changes

Add support for Drives, persistent storage that can store TBs of data and be mounted on sandboxes at a specific path. Drives support point-in-time, read-only snapshots. (#285)

Get started by creating a drive, then mount it on a sandbox:

sandbox drives get-or-create workspace-cache
sandbox create --name my-sandbox --mount workspace-cache:/data

Create a snapshot to mount the same drive on multiple sandboxes at a time:

sandbox drives get-or-create shared
sandbox create --name reader-1 --mount shared:/data:snapshot
sandbox create --name reader-2 --mount shared:/data:snapshot

Read the documentation to learn more: https://vercel.com/docs/sandbox/concepts/drives

Add opt-out usage telemetry and AI-agent attribution. The CLI now reports (#319)

anonymous usage events (subcommand, CLI version, platform, and the AI agent
driving the invocation, detected via detect-agent) to Vercel's telemetry
bridge, and tags API requests with the detected agent in the user-agent
header. Manage collection with sandbox telemetry status|enable|disable,
VERCEL_SANDBOX_TELEMETRY_DISABLED=1, or inspect events without sending via
VERCEL_TELEMETRY_DEBUG=1. Running as vercel sandbox respects the Vercel
CLI's own telemetry preference.

Patch Changes

Updated dependencies [6afca1fe55c9058416b622d1108123134bc5ff5e]:
@vercel/[email protected]

Minor Changes

read-only mounts have been replaced by snapshots: you can now mount the same drive on many sandboxes at once, using read-only snapshots: (#331)

const drive = await Drive.getOrCreate({ name: "test" });
await Sandbox.create({
  mounts: {
    "/data": drive.snapshot(),
  },
});

To mount a drive as read-write, simply pass in the drive object:

await Sandbox.create({
  mounts: {
    "/data": drive,
  },
});

Patch Changes

Updated dependencies [f45a57b1c6b022f751c3ea43cf23920e6e0d8489]:

• @vercel/[email protected]

Minor Changes

read-only mounts have been replaced by snapshots: you can now mount the same drive on many sandboxes at once, using read-only snapshots: (#331)

const drive = await Drive.getOrCreate({ name: "test" });
await Sandbox.create({
  mounts: {
    "/data": drive.snapshot(),
  },
});

To mount a drive as read-write, simply pass in the drive object:

await Sandbox.create({
  mounts: {
    "/data": drive,
  },
});

Patch Changes

Updated dependencies [f45a57b1c6b022f751c3ea43cf23920e6e0d8489]:
@vercel/[email protected]