# Run Paseo agents on Vercel Sandbox By Steven Van · 2026-10-28 The plugin needs Paseo 0.9 and Node.js 24, and stopped sandboxes keep files and history as snapshots that expire after 24 hours. Paseo agents can now run in the cloud on [Vercel]() Sandbox. The [Vercel Sandbox plugin]() supports fx, Codex, Claude Code, OpenCode and Pi, and is published by Vercel Labs. ## How sessions work An agent started in a sandbox from Paseo on a laptop can be controlled from a phone, including when the laptop is closed. Each sandbox runs its own Paseo daemon, and agents, terminals, files and session history live in the sandbox. A paired host keeps working when the controller is offline, though create, stop, resume, diagnose and delete need the controller online. Stopping a sandbox saves its filesystem as a snapshot. Resuming restores files and conversation history, but not running processes or an interrupted turn. Snapshots expire after 24 hours and the three most recent are kept. A host that reaches its session timeout shows as stopped and is not resumed automatically. ## Setup - Requires Node.js 24 or newer and Paseo 0.9 or newer on the controller daemon and client. - Enable plugins in Settings → Plugins in Paseo, then run paseo plugin add vercel-labs/paseo-vercel-sandbox. - In the plugin's settings, enter a Vercel token, team ID, project ID and an AI Gateway key. - Choose Create to start a sandbox in the iad1 region. The first Create takes a few minutes. - Choose Reveal pairing link and paste it into Hosts → Add host, once per host. Creating a host does not copy a repository into it. Workspaces go at /vercel/workspace/repo, and code has to be cloned or added there. Private repositories need their own Git credentials inside the sandbox. ## Keys and limits The AI Gateway key is entered once and reused for model requests across sessions. It is checked against AI Gateway before Create and added by the sandbox's egress firewall to requests to ai-gateway.vercel.sh, so agents inside the sandbox see a placeholder instead of the key. The Vercel token stays on the controller and is sent only to Vercel's API. Other outbound traffic from the sandbox is allowed, so code running there can still make billable Gateway requests through the firewall. Session timeout defaults to 1440 minutes (24 hours) and applies to hosts created after the setting is saved. On the **Hobby** plan, sandbox sessions are limited to 45 minutes, so the timeout should be set to 45 or less. Sandbox compute, storage and AI Gateway usage are billed to the user's Vercel account. ![Image from the Vercel announcement of Paseo agents running on Vercel Sandbox]() Image from the Vercel announcement of Paseo agents running on Vercel Sandbox ![Vercel]() Vercel The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config. [View Vercel →]() Sources [Original source]() [Read Run Paseo agents on Vercel Sandbox on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-run-paseo-agents-on-vercel-sandbox