← Plugins

Vercel Sandbox

Create and manage persistent Vercel Sandbox hosts for Codex, Claude Code, OpenCode, and Pi through Vercel AI Gateway.

$ paseo plugin add vercel-labs/vercel-sandbox
Report a bug
Vercel Sandbox screenshot 1

Vercel Sandbox creates persistent Vercel Sandboxes that each run their own Paseo daemon with Codex, Claude Code, OpenCode or Pi. You pair each sandbox with Paseo as a remote host, then create workspaces and agents on it like any other host. Agents reach their models through Vercel AI Gateway. The plugin is published by Vercel Labs.

The plugin runs on your controller daemon and adds a Vercel Sandboxes item to the sidebar with one host slot per agent. Create starts a sandbox in Vercel's iad1 region, installs pinned versions of the Paseo CLI and the agent CLIs from npm inside it, starts the sandbox daemon and prepares a relay pairing link. The first Create takes a few minutes. Choose Reveal pairing link, then paste it into Hosts → Add host once per host. Agents, terminals, files and session history live in the sandbox, so a paired host keeps working when the controller is offline. Create, stop, resume, diagnose and delete need the controller online.

Setup needs Node.js 24 or newer and Paseo 0.9 or newer on the controller daemon and client, with plugins enabled in Settings → Plugins. In the plugin's settings, enter a Vercel token, your Vercel team ID and project ID, and an AI Gateway key. Session timeout (minutes) defaults to 1440 (24 hours) and applies to hosts created after you save it. On the Hobby plan, Vercel Sandbox sessions are limited to 45 minutes, so set it to 45 or less there.

Credentials are stored in private files under the daemon user's Paseo plugin state directory. The Vercel token stays on the controller and is sent only to Vercel's API. The Gateway key is checked against AI Gateway before Create and placed in the sandbox's egress firewall policy, which adds it to requests to ai-gateway.vercel.sh. Agents inside the sandbox see a placeholder instead of the key. Other outbound traffic from the sandbox is allowed, so code running there can still make billable Gateway requests through the firewall.

Creating a host does not copy a repository into it. Create workspaces at /vercel/workspace/repo and clone or add your code there yourself; private repositories need their own Git credentials inside the sandbox.

Stop saves the sandbox filesystem as a snapshot and Resume restores files and session history, but not running processes or an interrupted turn. A host that reaches its session timeout shows as stopped and is never resumed automatically. Snapshots expire after 24 hours and the three most recent are kept. Delete asks you to type the agent ID and removes the sandbox and its snapshots. Sandbox compute, storage and AI Gateway usage are billed to your Vercel account.