Introducing Vercel Drives: persistent storage for agents

Agents often handle complex work that continues across runs. As that work evolves, they may need a new environment with different tools, runtimes, or compute. They should be able to continue working with the same files when they change environments.

We built Vercel Drives to keep an agent’s files independent of its execution environment. It is now generally available for Vercel Sandbox. Agents can mount the same drive in a new environment configured for the next task and continue where they left off.

Copy link to headingPersisting state with a drive

Create a drive once, then mount it when you create a sandbox. From the CLI:

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

Or from the Sandbox SDK:

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

In this example, everything under /workspace persists on the drive. Everything else belongs to the sandbox. The next sandbox that mounts the drive finds the repository, and anything else the agent wrote there, where the previous run left it.

The drive keeps the agent’s files independent of the sandbox running it. An agent can resume work in a new sandbox or switch runtimes without transferring its workspace. Other sandboxes can mount the same drive.

Copy link to headingSharing state across sandboxes

Agents can prepare files on a drive once and reuse them across sandboxes. If one agent builds a dataset on a drive, other agents can mount read-only copies to analyze the data or generate reports without rebuilding the dataset. They use the shared files as input and save their results separately.

Agents can also fork a drive to explore different approaches independently. Each fork starts with the drive’s contents and provides its own writable workspace. Agents can try different transformations of the dataset in parallel without changing the original or affecting one another. Forks don’t merge back into the original drive.

Forking is generally available.

Copy link to headingGet started

Vercel Drives is now generally available for Vercel Sandbox on all plans.

Drives default to 1 TiB, or 1 GiB on Hobby, with up to 16 TiB available. See the documentation for configuration, snapshots, and limits, or the changelog for what changed at GA.

Copy link to headingResources

• Read the Vercel Drives guide

• Deploy the Vercel Drives eve agent starter template in one click