vercel-sandbox

Run agent-browser with headless Chromium inside Vercel Sandbox microVMs.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/haxlys/skills --skill vercel-sandbox-haxlys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-sandbox
Source: https://github.com/haxlys/skills/tree/main/vendored/agent-browser/skill-data/vercel-sandbox
Command: npx skills add https://github.com/haxlys/skills --skill vercel-sandbox-haxlys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run agent-browser + headless Chrome inside ephemeral Vercel Sandbox microVMs. A Linux VM spins up on demand, executes browser commands, and shuts down. Works with any Vercel-deployed framework (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.).

Core Features & Use Cases

  • Ephemeral, isolated browser environments with fast startup via sandbox snapshots
  • Persist browser state across commands using the agent-browser pattern
  • Framework-agnostic browser automation for Next.js, SvelteKit, Nuxt, Remix, Astro, etc.

Quick Start

Install the sandbox package and run a script that launches a sandboxed Chromium session.

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 browser automation in Vercel Sandbox microVMs?

Headless browser automation in Vercel Sandbox microVMs works by spinning up an ephemeral Linux VM on demand, executing agent-browser commands with headless Chromium, and shutting down automatically. It requires the @vercel/sandbox package to manage VM lifecycle and isolation.

Can I use headless Chromium with Next.js, SvelteKit, Nuxt, Remix, or Astro deployments?

Yes, headless Chromium works with any Vercel-deployed framework including Next.js, SvelteKit, Nuxt, Remix, and Astro. The sandbox microVM runs framework-agnostic browser automation, ensuring your application stack remains compatible with ephemeral browser execution.

How do I persist browser state across multiple commands in an ephemeral sandbox?

To persist browser state across commands in an ephemeral sandbox, use the agent-browser pattern within the Vercel Sandbox microVM. This approach maintains session continuity during a run, while optional snapshots enable fast startup for subsequent isolated executions.

What is the best way to isolate browser execution environments for automated tasks?

The best way to isolate browser execution environments for automated tasks is using Vercel Sandbox microVMs, which provide per-run isolation. Each ephemeral Linux VM spins up on demand, executes headless Chromium commands independently, and shuts down securely.

Do I need the @vercel/sandbox package to run agent-browser in ephemeral environments?

Yes, you need the @vercel/sandbox package to run agent-browser in ephemeral environments. It manages the on-demand startup, per-run isolation, and optional snapshots required for executing headless Chromium securely within Vercel microVMs.

How does snapshotting improve startup time for headless Chromium in Vercel microVMs?

Snapshotting improves startup time for headless Chromium in Vercel microVMs by saving the VM state after initial boot. Optional snapshots allow subsequent browser automation runs to bypass cold starts, enabling fast execution for ephemeral environments.