Vercel Sandbox supports forking
By Steven Van ·
Sandbox.fork() clones a sandbox's latest snapshot, config and env vars, letting overrides apply per-field.
Vercel Sandbox now supports forking a running or stopped sandbox into a new one with Sandbox.fork(). The fork starts from the source's current snapshot and inherits its config and environment variables; if the source is running, the fork uses its last saved state rather than the live in-memory one. Any parameter passed to fork() overrides the inherited value, and if the source has no snapshot, the fork falls back to a fresh create using the source's runtime and config instead.
A fork takes about as long as creating a sandbox and has the same limits. Vercel suggests using it to branch an agent from a shared base, give each tenant its own copy of a template, or run variations of one setup in parallel. Forking is available in both the SDK and the CLI, via pnpm install @vercel/sandbox@latest or pnpm install -g sandbox@latest. More detail is in the announcement.