vercel-sandbox

Automate browser actions inside Vercel Sandbox microVMs using agent-browser.

21|Updated Aug 11, 2024
One-click install
npx skills add https://github.com/selfmail/selfmail --skill vercel-sandbox-selfmail
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vercel-sandbox
Source: https://github.com/selfmail/selfmail/tree/main/.agents/skills/vercel-sandbox
Command: npx skills add https://github.com/selfmail/selfmail --skill vercel-sandbox-selfmail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run browser automation inside ephemeral Vercel Sandbox microVMs so you can automate tasks that require Chromium without bundling a heavy browser into your app or risking flaky environments.

Core Features & Use Cases

  • Ephemeral Sandbox VM spins up on demand and runs headless Chrome for browser automation.
  • Persist browser sessions across commands to support multi-step workflows.
  • Pre-installed system dependencies and agent-browser to enable sub-second startups when using sandbox snapshots.

Quick Start

Run browser automation inside a Vercel Sandbox to open a URL and capture a screenshot.

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 an ephemeral cloud environment?▼

Run headless Chrome browser automation by spinning up an ephemeral Vercel Sandbox microVM on demand. This approach executes automated browser tasks without bundling a heavy browser into your application or risking flaky local environments.

Can I persist browser sessions across multiple automation steps in Vercel Sandbox?▼

Yes, you can persist browser sessions across commands in a Vercel Sandbox. This session persistence supports complex, multi-step workflows where subsequent browser actions rely on the state and cookies established by previous steps.

Does Vercel Sandbox work with any deployed framework for browser automation?▼

Vercel Sandbox targets any Vercel-deployed framework that requires headless Chrome, persistent sessions, or isolated environments. It uses agent-browser to automate actions inside the microVMs regardless of the underlying web framework.

What do I need to authenticate and run Vercel Sandbox browser automation locally?▼

To run Vercel Sandbox browser automation locally, you need a Vercel Sandbox runtime and specific environment variables configured for authentication. These credentials ensure your local agent-browser commands can securely access the ephemeral microVMs.

Why use a Vercel Sandbox microVM instead of bundling headless Chrome into my app?▼

Using a Vercel Sandbox microVM isolates browser automation tasks from your main application. This prevents flaky environments caused by system dependency conflicts and enables sub-second startups by leveraging pre-installed dependencies and sandbox snapshots.

How do I open a URL and capture a screenshot using Vercel Sandbox browser automation?▼

Open a URL and capture a screenshot by triggering browser automation inside a Vercel Sandbox. The ephemeral environment launches headless Chrome via agent-browser, executes the navigation, and returns the captured screenshot output.