vercel-sandbox

Runs headless Chrome browser automation inside ephemeral Vercel Sandbox microVMs.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Alwahdi/mikrotik-whisperer --skill vercel-sandbox-alwahdi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-sandbox
Source: https://github.com/Alwahdi/mikrotik-whisperer/tree/main/.agents/skills/vercel-sandbox
Command: npx skills add https://github.com/Alwahdi/mikrotik-whisperer --skill vercel-sandbox-alwahdi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Running headless Chrome from a Vercel-deployed app is blocked by serverless binary size limits and missing system libraries. This Skill spins up an ephemeral Vercel Sandbox microVM with Chromium and agent-browser pre-installed, so browser automation works from any Vercel framework without infrastructure changes. ## Core Features & Use Cases - Ephemeral Browser VMs: Create on-demand Linux microVMs that execute agent-browser commands (open, snapshot, fill, click, screenshot) and shut down automatically. - Sandbox Snapshots: Pre-build a VM image with Chromium system dependencies and agent-browser for sub-second startup instead of ~30s installs. - Multi-Step Automation: Persist browser sessions across commands to fill forms, click elements, wait for network idle, and capture screenshots as base64. - Use Case: Add a scheduled Vercel Cron route that opens a competitor's pricing page daily, captures an accessibility snapshot, and stores the results for change monitoring. ## Quick Start Use the vercel-sandbox skill to open a URL in headless Chrome inside a Vercel Sandbox and return a screenshot of the page.

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 app?

Use the @vercel/sandbox SDK to create an ephemeral microVM, install Chromium system dependencies via dnf, then run agent-browser commands inside it. This bypasses serverless binary size limits that prevent bundling Chrome directly.

What is a Vercel Sandbox snapshot and why use one?

A sandbox snapshot is a saved VM image with system dependencies, agent-browser, and Chromium pre-installed. Booting from a snapshot reduces startup from roughly 30 seconds of installs to sub-second, making it recommended for production deployments.

Does Vercel Sandbox browser automation work with Next.js, SvelteKit, and Nuxt?

Yes, the pattern works identically across frameworks including Next.js, SvelteKit, Nuxt, Remix, and Astro. Only the server-side code location differs, such as route handlers in Next.js or server routes in Nuxt.

How do I authenticate the Vercel Sandbox SDK locally?

Set VERCEL_TOKEN, VERCEL_TEAM_ID, and VERCEL_PROJECT_ID environment variables for local development. On Vercel deployments, authentication happens automatically via OIDC with no configuration needed.

Can I schedule recurring browser tasks with Vercel Sandbox?

Yes, combine the sandbox pattern with Vercel Cron Jobs by defining a cron route that creates a sandbox, runs agent-browser commands, and processes results. Configure the schedule in vercel.json.