vercel-sandbox

Run headless Chrome browser automation inside ephemeral Vercel Sandbox microVMs.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/dev-khoi/AURA-conHack-2026 --skill vercel-sandbox-dev-khoi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vercel-sandbox
Source: https://github.com/dev-khoi/AURA-conHack-2026/tree/main/.opencode/skills/vercel-sandbox
Command: npx skills add https://github.com/dev-khoi/AURA-conHack-2026 --skill vercel-sandbox-dev-khoi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @vercel/sandbox, agent-browser.

What problem does it solve? Running headless Chrome inside serverless functions is blocked by binary size limits and missing system libraries. This Skill shows how to run agent-browser and Chromium inside Vercel Sandbox microVMs, giving any Vercel-deployed app full browser automation without infrastructure work. ## Core Features & Use Cases - Ephemeral Browser VMs: Spin up an isolated Linux microVM on demand, run browser commands, and shut it down automatically. - Sandbox Snapshots: Pre-install Chromium system dependencies and agent-browser into a reusable VM image for sub-second startup instead of ~30 second cold installs. - Multi-Step Automation: Persist browser sessions across commands to open pages, fill forms, click elements, capture screenshots, and extract accessibility snapshots. - Use Case: Add a Vercel Cron Job that opens a competitor's pricing page every morning, captures an accessibility snapshot, and stores the results for change detection. ## Quick Start Use the vercel-sandbox skill to open a URL in headless Chrome inside a Vercel Sandbox and return a screenshot plus the page title.

Frequently Asked Questions about vercel-sandbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run headless Chrome in a Vercel serverless function?▼

Use the @vercel/sandbox SDK to create a microVM, install Chromium system dependencies via dnf, install agent-browser, then run browser commands with sandbox.runCommand. This avoids serverless binary size limits entirely.

How to speed up Vercel Sandbox browser startup time?▼

Create a sandbox snapshot that pre-installs Chromium system dependencies, agent-browser, and the browser binary, then set AGENT_BROWSER_SNAPSHOT_ID. Booting from the snapshot reduces startup from about 30 seconds to sub-second.

Does Vercel Sandbox browser automation work with Next.js and other frameworks?▼

Yes, the pattern works identically across Next.js, SvelteKit, Nuxt, Remix, and Astro. The only difference is where the server-side code lives, such as route handlers, server actions, or server API routes.

How does authentication work for the Vercel Sandbox SDK?▼

On Vercel deployments the SDK authenticates automatically via OIDC using VERCEL_OIDC_TOKEN. For local development, set VERCEL_TOKEN, VERCEL_TEAM_ID, and VERCEL_PROJECT_ID environment variables.

Can I schedule recurring browser automation tasks on Vercel?▼

Yes, combine the sandbox browser pattern with Vercel Cron Jobs. Define a cron route that runs agent-browser commands inside a sandbox and register the schedule in vercel.json.