vercel-sandbox

Runs headless Chrome and agent-browser in ephemeral Vercel Sandbox microVMs for browser automation from deployed apps.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Chris-Maskey/opencode-config --skill vercel-sandbox-chris-maskey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-sandbox
Source: https://github.com/Chris-Maskey/opencode-config/tree/main/skills/vercel-sandbox
Command: npx skills add https://github.com/Chris-Maskey/opencode-config --skill vercel-sandbox-chris-maskey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reliable pattern to run headless Chrome and agent-browser inside ephemeral Vercel Sandbox microVMs so browser automation can be executed from any Vercel-deployed app without binary size limits or local Chrome dependencies.

Core Features & Use Cases

  • Ephemeral Browser VMs: Boot a Linux microVM on demand, run agent-browser commands, and shut down to isolate runs.
  • Sandbox Snapshots for Fast Startup: Pre-built sandbox snapshots include Chromium and dependencies for sub-second startup.
  • Persistent Sessions & Multi-Step Flows: Keep the sandbox alive across multiple commands to perform full automation sequences (open pages, fill forms, take screenshots, accessibility snapshots).
  • Framework & Workflow Integration: Use from Next.js, SvelteKit, Nuxt, Remix, Astro server code or from Vercel Cron Jobs for scheduled tasks.
  • Authentication Options: Works with Vercel OIDC on deployments or explicit tokens/team/project IDs for local development.

Quick Start

Use the vercel-sandbox skill to open https://example.com, take a screenshot, and return the image as a base64 string.

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 Vercel Sandbox microVMs from a Next.js app?

You run headless Chrome in Vercel Sandbox by executing agent-browser commands from your Next.js server-side code, booting an ephemeral Linux microVM to isolate browser automation without local dependencies.

What is a Vercel Sandbox snapshot and how does it speed up browser automation?

A Vercel Sandbox snapshot is a pre-built microVM state that includes Chromium and system libraries, enabling sub-second startup times for headless Chrome browser automation tasks.

Can I use headless Chrome with Vercel Cron Jobs for scheduled scraping tasks?

Yes, you can use headless Chrome with Vercel Cron Jobs to execute scheduled browser automation, taking screenshots or performing scraping tasks within ephemeral Sandbox microVMs.

Does browser automation in Vercel Sandbox support persistent sessions for multi-step form automation?

Yes, Vercel Sandbox supports persistent sessions by keeping the microVM alive across multiple commands, enabling full multi-step automation sequences like opening pages, filling forms, and taking accessibility snapshots.

How do I authenticate Vercel Sandbox requests for local development versus deployment?

For local development, authenticate Vercel Sandbox requests using explicit tokens with team and project IDs, while deployed applications can authenticate automatically via Vercel OIDC.

What frameworks are supported for server-side browser automation using Vercel Sandbox?

Server-side browser automation using Vercel Sandbox is supported in Next.js, SvelteKit, Nuxt, Remix, and Astro frameworks, allowing you to run headless Chrome directly from your application code.