vercel-sandbox

Runs headless Chrome browser automation inside ephemeral Vercel Sandbox microVMs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Running headless Chrome inside Vercel-deployed apps is blocked by serverless binary size limits and missing system libraries. This Skill provides a pattern for spinning up ephemeral Vercel Sandbox microVMs with agent-browser and Chromium pre-installed, so any Vercel app can perform browser automation without infrastructure changes. ## Core Features & Use Cases - Ephemeral Browser VMs: Create on-demand Linux microVMs via the @vercel/sandbox SDK that run agent-browser commands and shut down automatically. - Sandbox Snapshots: Pre-build VM images with Chromium system dependencies for sub-second startup instead of ~30s installs. - Full Automation Workflows: Capture screenshots, extract accessibility snapshots, fill forms, and run multi-step interactions, with support for Vercel Cron for scheduled tasks. - Use Case: A Next.js app needs to screenshot competitor pricing pages daily. Use this Skill to create a sandbox, run agent-browser commands, return the screenshot as base64, and schedule it with a Vercel Cron job. ## 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 and agent-browser, then run browser commands via sandbox.runCommand. This avoids serverless binary size limits since Chrome runs inside the sandbox VM, not your function.

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, SvelteKit, and Nuxt?

Yes, the pattern works identically across frameworks including 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 do I authenticate the Vercel Sandbox SDK locally?

On Vercel deployments, the SDK authenticates automatically via OIDC. For local development, set the VERCEL_TOKEN, VERCEL_TEAM_ID, and VERCEL_PROJECT_ID environment variables, which are passed into Sandbox.create calls.

Can I schedule recurring browser automation tasks on Vercel?

Yes, combine the sandbox browser 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 with a crons entry.