sandbox-v2-lifecycle

por vercel

Expertise em ciclo de vida do Vercel Sandbox v2 para vercel-openclaw: criação/retomada/parada/exclusão de sandbox OpenClaw persistente nomeada, verdade de salvamento automático persistente, manual…

npx skills add https://github.com/vercel-labs/vercel-openclaw --skill sandbox-v2-lifecycle

Sandbox v2 Lifecycle

Use this skill for vercel-openclaw sandbox lifecycle, restore, stop, reset, hot-spare, worker sandbox, and debug timing work.

Source Of Truth

Official Vercel Sandbox v2 docs are authoritative. Repo docs or agent guidance that assumes v1/manual snapshot restore is stale unless already updated.

Load references only as needed:

  • references/vercel-sandbox-v2-persistent.md — persistent sandbox auto-save/resume/name/session model.
  • references/vercel-sandbox-v2-sdk.md — SDK calls, resume flags, delete, command behavior, and network policy notes.
  • references/vercel-sandbox-v2-snapshots.md — manual Snapshot API semantics.
  • references/vercel-openclaw-lifecycle-map.md — repo-specific invariants and owner files.

Core Model

  • Main OpenClaw runtime is one named persistent sandbox.
  • Persistent stop() auto-saves filesystem state; no manual snapshot() is needed for normal stop.
  • Normal wake resumes by name with Sandbox.get({ name, resume: true }) through the repo controller.
  • resume defaults false; use resume:false for observation/status reconciliation.
  • Commands may auto-resume stopped persistent sandboxes; stop() and update() do not.
  • Manual snapshot() is explicit/debug/checkpoint only. It shuts the sandbox down; do not call stop() afterward.
  • delete() permanently removes the persistent sandbox and its sessions/snapshots.
  • Worker/debug sandboxes are short-lived; pass persistent:false.

Repo Invariants

  • Preserve one persistent OpenClaw sandbox, Redis metadata, channel wake/restore, and short-lived workers.
  • Keep SDK access behind src/server/sandbox/controller.ts except documented raw SDK debug routes.
  • Distinguish host metadata status, SDK status/session, gateway readiness, persistent auto-saved state, and manual Snapshot APIs.
  • Do not use manual snapshotId as the normal restore gate.
  • Preserve resume:false during snapshotting/stopped observation.
  • Keep lifecycle locks and fail-closed firewall behavior.

Workflow

  1. Read lat.md/sandbox-lifecycle.md, docs/lifecycle-and-restore.md, and relevant references from this skill.
  2. Inspect src/server/sandbox/lifecycle.ts, controller.ts, restore-attestation.ts, hot-spare.ts, and worker sandbox code.
  3. Classify whether the change affects persistent resume, manual snapshots, reset/delete, workers, or debug diagnostics.
  4. Patch the smallest surface that fixes the v2 truth model.
  5. Add or adjust targeted tests before broad verification.

Verification

Run the narrowest covering test first, then broader gates for lifecycle changes:

node --import tsx --test src/server/sandbox/restore-attestation.test.ts
pnpm run test:lifecycle
pnpm run typecheck
pnpm run lint
lat check

When touching launch verification or preflight, also run pnpm run verify:observability-pass.

Mais skills de vercel

benchmark-sandbox
vercel
Executa cenários de avaliação do vercel-plugin em Vercel Sandboxes em vez de painéis locais do WezTerm. Provisiona microVMs efêmeras com Claude Code + plugin pré-instalado,…
official
emil-design-eng
vercel
Esta habilidade codifica a filosofia de Emil Kowalski sobre polimento de UI, design de componentes, decisões de animação e os detalhes invisíveis que fazem o software parecer ótimo.
official
vercel-react-best-practices
vercel
Diretrizes de otimização de desempenho para React e Next.js da Vercel Engineering. Esta habilidade deve ser usada ao escrever, revisar ou refatorar React/Next.js…
official
vercel-react-best-practices
vercel
Diretrizes de otimização de desempenho para React e Next.js da Vercel Engineering. Esta skill deve ser usada ao escrever, revisar ou refatorar React/Next.js…
official
write-guide
vercel
Produza um guia técnico que ensine um caso de uso do mundo real por meio de exemplos progressivos. Os
official
release
vercel
Liberar vercel-plugin — executar gates, incrementar versão, gerar artefatos, commitar e fazer push. Use quando solicitado a "liberar", "enviar", "incrementar e fazer push" ou "cortar uma liberação".
official
deepsec
vercel
Execute o DeepSec em um checkout de projeto Vercel do dev3000. Use para configuração DeepSec com um clique, inicialização de contexto do projeto, processamento limitado de primeira passagem e…
official
backport-pr
vercel
Fazer backport de um pull request do Next.js já mesclado, do canary para uma branch de release anterior, como next-16-2. Use quando o usuário pedir para fazer backport, cherry-pick ou abrir um…
official