vercel-sandbox

Run agent-browser with headless Chrome inside Vercel Sandbox.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser tasks inside Vercel Sandbox by running agent-browser with headless Chrome. 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

  • On-demand Linux VM in Vercel Sandbox to run agent-browser with headless Chrome
  • Persistent browser sessions across commands
  • Sandbox snapshots for sub-second startup
  • Framework-agnostic compatibility across Next.js, SvelteKit, Nuxt, Remix, Astro, etc.
  • Automatic authentication via OIDC on Vercel, with local dev options.

Quick Start

Spin up a Vercel Sandbox and run agent-browser to automate a URL in a headless Chrome instance.

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 Sandbox?

You can run headless Chrome in a Vercel Sandbox by using this Skill to spin up an on-demand Linux VM that executes agent-browser commands and shuts down automatically after task completion.

Can I use browser automation with my Next.js or SvelteKit app on Vercel?

Yes, browser automation works with any Vercel-deployed framework including Next.js, SvelteKit, Nuxt, Remix, and Astro by running agent-browser with headless Chrome inside the Vercel Sandbox environment.

Do I need the @vercel/sandbox package for local development authentication?

Yes, local development requires the @vercel/sandbox package alongside OIDC-based authentication on Vercel to successfully authorize and execute browser automation commands within your local environment.

How do Vercel Sandbox snapshots achieve sub-second startup for browser sessions?

Vercel Sandbox snapshots achieve sub-second startup by saving the Linux VM state, allowing persistent browser sessions across commands to resume instantly without reinitializing headless Chrome.

What is the best way to maintain persistent browser sessions across automation commands?

The best way to maintain persistent browser sessions is using Vercel Sandbox with headless Chrome, which keeps the Linux VM environment alive between agent-browser commands until explicitly shut down.

Are there limitations when running headless Chrome in a Vercel Sandbox microvm?

A limitation of running headless Chrome in a Vercel Sandbox microvm is that the Linux VM spins up on demand and shuts down, requiring sandbox snapshots to preserve session state for fast subsequent startups.