Vercel Sandbox v2 operator

Look up Vercel Sandbox commands, configuration, lifecycle controls, and focused operations across lifecycle, commands and files, runtimes and snapshots, networking and exposure, security and limits. Use when the user wants a concise reference instead of a guided workflow.

Execute Vercel Sandbox commands and operate files with explicit argv, working directories, environment allowlists, streaming output, upload, download, atomic writes, and path validation. Use when running code in a sandbox, transferring files, streaming logs, or modifying a sandbox filesystem.

Inspect Vercel Sandbox package and CLI versions, project and account context, configuration, environment variable names, resources or runs, persistence, limits, and safe checks without changing anything. Use before Vercel Sandbox work, when the target is uncertain, or when the user asks what is configured.

Connect Vercel Sandbox to application runtimes, identity, storage, external events, observability, CI, and deployment while preserving isolation, durability, credential, and action boundaries. Use when Vercel Sandbox crosses another system or must operate consistently through production.

Operate Vercel Sandbox v2 lifecycle including creation, lookup, persistence, timeout, reconnection, stop, exit, and deterministic cleanup. Use when creating or resuming a sandbox, changing lifetime, inspecting state, or cleaning up persistent remote compute.

Operate Vercel Sandbox networking including outbound requests, DNS, development servers, port exposure, live preview URLs, request proxying, and network restrictions. Use when a sandbox needs network access, must run a server, expose a preview, or cannot reach a dependency.

Configure Vercel Sandbox runtimes, dependency installation, environment images, snapshots, restore, reproducibility, and safe reuse boundaries. Use when choosing Node or Python runtime, speeding startup, capturing a prepared environment, or restoring consistent sandboxes.

Harden Vercel Sandbox use with threat modeling, process and filesystem isolation, sudo controls, compute and storage limits, timeouts, abuse prevention, audit logs, and incident cleanup. Use when running untrusted code, reviewing sandbox safety, setting resource controls, or responding to suspicious execution.

Install and configure Vercel Sandbox from zero with project-local packages, exact account and environment scope, server-only authentication, baseline limits and persistence, one minimal operation, and bounded verification. Use when a project has no Vercel Sandbox setup or the user explicitly asks to initialize it.

Diagnose Vercel Sandbox failures involving versions, scope, authentication, resource or run state, persistence, retries, timeouts, isolation, networking, observability, usage, and deployment without masking the original error. Use when Vercel Sandbox fails, stalls, resumes incorrectly, or causes unexpected remote effects.