vercel-sandbox-runtime

Configure Union Street agents to run inside Vercel Sandbox microVMs with auth, persistence, and wakeups.

Updated May 6, 2026
One-click install
npx skills add https://github.com/UnionStreetAI/unionstreet --skill vercel-sandbox-runtime-unionstreetai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vercel-sandbox-runtime
Source: https://github.com/UnionStreetAI/unionstreet/tree/main/plugins/runtime-vercel/skills/vercel-sandbox-runtime
Command: npx skills add https://github.com/UnionStreetAI/unionstreet --skill vercel-sandbox-runtime-unionstreetai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running delegated agent tasks on the head node lacks isolation and scalability. This Skill guides the configuration of Union Street agents to execute inside isolated Vercel Sandbox microVMs, handling authentication, persistence, and Lash runtime wakeups correctly. ## Core Features & Use Cases - Auth Mode Selection: Choose between native OIDC (via VERCEL_OIDC_TOKEN) and access-token auth requiring VERCEL_TEAM_ID, VERCEL_PROJECT_ID, and VERCEL_TOKEN, with strict rules against partial configuration. - Runtime Wake Shape: Create or resume a sandbox, start the Union Street runtime API inside it, expose the control port, and call POST /api/peers/:target/wake while preserving caller, message, trace, thread, chain, and wakeKind. - Persistence Policy: Default to ephemeral sandboxes for one-off delegated tasks, use named persistent sandboxes only when explicitly configured, prefer snapshots for warm starts, and tag sandboxes with unionstreet, profile, plugin, and trace labels. - Use Case: A manager agent delegates a compute-heavy task to a direct report; the provider spins up a tagged ephemeral Vercel Sandbox, wakes the agent over Lash, and tears the sandbox down after the result returns. ## Quick Start Ask the agent to configure a Union Street profile to run delegated tasks in a Vercel Sandbox using OIDC auth and ephemeral sandbox persistence.

Frequently Asked Questions about vercel-sandbox-runtime

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

FAQPage Schema
How do I run Union Street agents in a Vercel Sandbox?▼

Configure the runtime provider to create or resume a sandbox, start the Union Street runtime API inside it, expose the control port, then call POST /api/peers/:target/wake. The wake request must preserve caller, message, trace, thread, chain, and wakeKind.

Which Vercel auth mode should I use for sandbox runtimes?▼

Prefer OIDC when VERCEL_OIDC_TOKEN is available, which is the native Vercel path via vercel link and vercel env pull. Use access_token auth only when Union Street runs outside Vercel, requiring VERCEL_TEAM_ID, VERCEL_PROJECT_ID, and VERCEL_TOKEN.

Can I proceed with only some Vercel access token variables set?▼

No. Access-token auth requires all three environment variables: VERCEL_TEAM_ID, VERCEL_PROJECT_ID, and VERCEL_TOKEN. Do not continue with partial configuration, and do not pass VERCEL_TOKEN to agent code unless the task explicitly calls Vercel APIs.

When should I use persistent versus ephemeral Vercel Sandboxes?▼

Default to ephemeral sandboxes for one-off delegated tasks. Use named persistent sandboxes only when the agent config explicitly requests durable state, and prefer snapshots for warm starts and reproducible base environments.

What tags should Vercel Sandboxes have for Union Street agents?▼

Tag sandboxes with at least unionstreet=true, profile=<agent>, and plugin=runtime-vercel. When a sandbox is created for a delegated wake, also add trace=<lash-trace> so delegated work remains auditable.