vercel-sandbox

Run agent-browser with headless Chrome inside ephemeral Vercel Sandbox microVMs.

3|2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/tysonthomas9/loomcli --skill vercel-sandbox-tysonthomas9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-sandbox
Source: https://github.com/tysonthomas9/loomcli/tree/main/internal/webui/frontend/.agents/skills/vercel-sandbox
Command: npx skills add https://github.com/tysonthomas9/loomcli --skill vercel-sandbox-tysonthomas9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @vercel/sandbox.

What problem does it solve?

This skill enables running browser automation inside ephemeral Vercel Sandbox microVMs, letting you execute agent-browser with headless Chrome directly from a Vercel-hosted app without shipping large browser binaries. It removes the complexity of managing dedicated browser runners and CI-only environments, giving you on-demand browser power for modern web apps.

Core Features & Use Cases

  • Run agent-browser + headless Chrome inside on-demand Vercel Sandboxes for isolated browser automation.
  • Maintain persistent browser sessions across commands while the sandbox is active, with fast startup using snapshots.
  • Use cases include automated UI testing, in-app browser automation, performance measurements, and end-to-end workflow simulations across frameworks like Next.js, SvelteKit, Nuxt, Remix, and Astro.

Quick Start

Install the sandbox package and run a sample script to launch a sandboxed browser 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 Chrome browser automation in a Vercel app?

You can run headless Chrome browser automation in a Vercel app by using ephemeral Vercel Sandbox microVMs. This approach executes agent-browser sessions directly from your Vercel-hosted application without shipping large browser binaries.

Does Vercel Sandbox support persistent browser sessions for automated testing?

Yes, Vercel Sandbox supports persistent browser sessions for automated testing. It maintains browser state across commands while the sandbox is active and uses snapshots for fast startup during isolated UI automation.

Can I use Vercel Sandbox for browser automation with Next.js, SvelteKit, Nuxt, Remix, and Astro?

Yes, you can use Vercel Sandbox for browser automation with Next.js, SvelteKit, Nuxt, Remix, and Astro. It provisions isolated microVMs tailored for these frameworks to execute end-to-end workflow simulations.

What is the best way to execute UI automation without managing dedicated browser runners?

The best way to execute UI automation without dedicated browser runners is using on-demand Vercel Sandboxes. This removes the complexity of CI-only environments by provisioning ephemeral microVMs for your browser power needs.

Do I need the @vercel/sandbox package and Chromium dependencies to provision a sandboxed browser?

Yes, you need the @vercel/sandbox package and Chromium system dependencies to provision a sandboxed browser. Environment configuration is also required to run agent-browser tooling with headless Chrome inside the microVMs.