vercel-sandbox

Runs headless Chrome browser automation inside ephemeral Vercel Sandbox microVMs.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/dsgalkar/dnyaneshwar_portfolio --skill vercel-sandbox-dsgalkar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-sandbox
Source: https://github.com/dsgalkar/dnyaneshwar_portfolio/tree/main/.agents/plugins/vercel/skills/vercel-sandbox/upstream
Command: npx skills add https://github.com/dsgalkar/dnyaneshwar_portfolio --skill vercel-sandbox-dsgalkar

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, executes browser commands, and shuts the VM down when finished. ## Core Features & Use Cases - Ephemeral Browser VMs: Create on-demand Linux microVMs via the @vercel/sandbox SDK that run agent-browser commands and persist state across multi-step workflows. - Sandbox Snapshots: Pre-build a VM image with Chromium system dependencies and agent-browser for sub-second startup instead of ~30 second installs. - Screenshots & Accessibility Snapshots: Capture page screenshots as base64 and dump interactive accessibility trees for element targeting. - Use Case: Add a Vercel Cron Job that opens a competitor's pricing page every morning, takes an accessibility snapshot, and stores the results for change detection. ## Quick Start Ask the agent to set up browser automation in your Vercel app using the Sandbox pattern, starting with installing @vercel/sandbox and creating a snapshot for fast startup.

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. The sandbox persists between commands and shuts down when your workflow finishes.

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, similar to a Docker image. Booting from a snapshot reduces startup from about 30 seconds to sub-second, which is recommended for production deployments.

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 in Next.js or +server.ts files in SvelteKit.

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 schedule in vercel.json and placing the browser automation logic in the cron route handler. Each run spins up a fresh sandbox, executes commands, and shuts down.