vercel-sandbox

Launch headless Chrome inside Vercel Sandbox microVMs for browser automation.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/dev-khoi/conHack-2026 --skill vercel-sandbox-dev-khoi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-sandbox
Source: https://github.com/dev-khoi/conHack-2026/tree/main/.opencode/skills/vercel-sandbox
Command: npx skills add https://github.com/dev-khoi/conHack-2026 --skill vercel-sandbox-dev-khoi

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Run browser automation for Vercel deployments by launching headless Chrome inside ephemeral Vercel Sandbox microVMs, removing the need for locally installed Chromium or large binaries and enabling on-demand isolation.

## Core Features & Use Cases

  • Ephemeral Vercel Sandbox VMs with on-demand Chromium to run browser tasks.
  • Persistent browser sessions across multiple commands within a single sandboxed environment.
  • Framework-agnostic support for Next.js, SvelteKit, Nuxt, Remix, Astro, and other Vercel-compatible apps.
  • Secure, isolated environments with fast startup via sandbox snapshots when available.

### Quick Start Invoke a sandboxed browser session from your Vercel app to begin automating browser tasks.

Frequently Asked Questions about vercel-sandbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run browser automation tests in Vercel sandboxes?

You can run browser automation tests in Vercel sandboxes by launching a headless Chrome instance inside an ephemeral Vercel Sandbox microVM. This removes the need for locally installed Chromium and provides on-demand isolation for executing browser tasks.

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

Yes, headless Chrome works with Next.js, SvelteKit, Nuxt, Remix, and Astro deployments. The sandboxed browser setup is framework-agnostic, supporting any Vercel-compatible app for automating browser tasks.

Do I need Vercel Sandbox access and an agent-browser setup to run headless Chrome?

Yes, you need Vercel Sandbox access and an agent-browser setup to run headless Chrome. These are required to initialize, reuse, and terminate the sandboxed browser environment during automation tasks.

What is the best way to maintain persistent browser sessions across multiple commands in a cloud VM?

The best way to maintain persistent browser sessions across multiple commands in a cloud VM is using a Vercel Sandbox. It supports persistent sessions within a single sandboxed environment, enabling continuous browser automation across sequential commands.

Why use an ephemeral Vercel Sandbox microVM instead of a local Chromium installation for browser tests?

Using an ephemeral Vercel Sandbox microVM instead of local Chromium provides secure, isolated environments with fast startup via sandbox snapshots. It removes large local binaries and enables on-demand isolation for framework-agnostic browser tasks.