vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or
Security Assessment
Detected risks:
About vercel-sandbox
The vercel-sandbox skill enables developers to run agent-browser with headless Chrome inside ephemeral Vercel Sandbox microVMs, providing seamless browser automation from any Vercel-deployed application. By leveraging microVMs, this skill allows tasks that require a full browser environment without the constraints of binary size limits or local infrastructure setup. The sandbox spins up a Linux VM on demand, executes browser commands, and shuts down automatically, ensuring isolated and efficient execution of browser automation tasks.
This skill offers core capabilities such as persistent browser sessions across commands, the ability to pre-install Chromium system dependencies using sandbox snapshots for sub-second startup, and straightforward integration with frameworks like Next.js, SvelteKit, Nuxt, Remix, and Astro. It supports running commands via agent-browser, including opening pages, taking screenshots, and retrieving page titles. Developers can interact programmatically with the sandbox using TypeScript, manage credentials securely via environment variables, and leverage snapshots to optimize performance and reduce initialization time.
vercel-sandbox is ideal for developers who need reliable browser automation within Vercel applications, particularly when testing, scraping, or performing automated web interactions. It targets users building modern web frameworks on Vercel who want headless Chrome without dealing with binary limitations or local setup. Typical use cases include generating screenshots of web pages, automating accessibility testing, performing browser-based integration tests, or running isolated browser environments for ephemeral tasks that require sandboxed execution.
FAQ
Which frameworks are compatible with vercel-sandbox?
vercel-sandbox works with any framework deployed on Vercel, including Next.js, SvelteKit, Nuxt, Remix, and Astro.
How do I install the required dependencies for Chromium in the sandbox?
You can pre-install dependencies using sandbox snapshots, or manually install the system libraries required by Chromium via the provided command in the core pattern.
Can vercel-sandbox maintain persistent browser sessions?
Yes, it supports persistent browser sessions across commands when using agent-browser inside the sandbox VM.
What credentials are needed to use the sandbox?
Environment variables VERCEL_TOKEN, VERCEL_TEAM_ID, and VERCEL_PROJECT_ID are required for authentication and sandbox creation.
Are there any limitations on running headless Chrome in vercel-sandbox?
The skill runs Chrome inside ephemeral VMs with all necessary system dependencies, but performance may be influenced by sandbox initialization time and the use of snapshots for faster startup.
Install vercel-sandbox
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
vercel-labs/agent-browser