Agents frequently run work that spans multiple executions, and a task that outgrows its runtime may need to move to an environment with different tools or compute. Vercel Drives is designed so those files travel with the agent rather than staying pinned to a single environment. The feature is now generally available for Vercel Sandbox.

Declaring a drive

A drive is created once and then mounted at sandbox creation time. From the CLI:

sandbox drives get-or-create agent-workspace
sandbox create --mount agent-workspace:/workspace

From the Sandbox SDK:

import { Sandbox, Drive } from '@vercel/sandbox';
const drive = await Drive.getOrCreate({ name: 'agent-workspace' });
const sandbox = await Sandbox.create({
  mounts: { '/workspace': drive },
});
await sandbox.runCommand('git', ['clone', repoUrl, '/workspace/repo']);

Whatever the agent writes under /workspace lives on the drive; everything outside that path belongs to the sandbox. A later sandbox that mounts the same drive sees the repository and any other files the previous run left behind. Because the files are decoupled from the environment, an agent can resume in a new sandbox or move to a different runtime without moving its workspace, and multiple sandboxes can mount one drive.

Reuse and parallel exploration

Work prepared on a drive can be shared. An agent that builds a dataset there allows other agents to mount read-only copies, analyze or report on the data without rebuilding it, and write their own results elsewhere.

For divergent work, a drive can be forked. A fork inherits the drive's contents but exposes its own writable workspace, letting agents apply different transformations to the same data in parallel while leaving the original and each other untouched. Forks do not merge back into the source drive. Forking is generally available.

Availability and limits

Drives ship generally available for Vercel Sandbox on all plans. Default capacity is 1 TiB, or 1 GiB on Hobby, and up to 16 TiB is available. Configuration, snapshots, and limits are covered in the documentation; the changelog describes what changed at GA.

Further reading