| name | vercel-sandbox |
| description | Investigate Vercel Sandbox lifecycle, timeout, snapshot, and persistence behavior. Use when users ask about Vercel Sandbox, `@vercel/sandbox`, `Sandbox.create`, `Sandbox.get`, why files disappeared, how snapshots differ from persistence, or whether Vercel's persistent sandbox beta applies. |
Investigate Vercel Sandbox using current official docs, installed SDK contracts, and only then any consumer-specific integration code.
Step 1: Classify the request
Pick the narrowest reference set before answering:
| Request type | Read first |
|---|
| SDK/API behavior, lifecycle semantics, snapshots, stable vs beta persistence | references/api-surface.md |
| Product-level usage patterns and architectural choices | references/common-use-cases.md |
| Broken behavior, confusing docs, missing files, or suspected persistence bugs | references/troubleshooting-workarounds.md |
If the task spans categories, load only the relevant files above.
Step 2: Establish which sandbox model applies
- Inspect the installed
@vercel/sandbox version and local types before trusting any doc page or changelog.
- If local types only expose
sandboxId, Sandbox.get({ sandboxId }), extendTimeout, and snapshot-backed source, treat the runtime as stable 1.x ephemeral sandboxes.
- If local code and types expose named sandboxes,
name, persistent, session updates, or automatic resume after stop, treat the runtime as the persistent beta model.
- Qualify time-sensitive claims with a date or retrieval note.
Step 3: Apply core guardrails
