Back to catalog / Integrations
Migrate stable Sandbox to @next: audit incompatible protocols before cutover
Plan package/image alignment, API changes, validation, and immediate production cutover.
Skills
Read the official migration/preview docs and installed @next types; inventory stable APIs. Worker package and container image must use the same @next line. `await sandbox.exec(argv)` starts a process and returns a handle; retrieve output separately. Argv does not invoke a shell, handles have no stdin, and wait timeout/AbortSignal does not kill the process. Replace sessions/transport/terminal/interpreter APIs, then typecheck and test long processes/terminals. Get user approval before production: stable/@next protocols are incompatible and production requires immediate rollout, which may stop existing processes.
Permissions
Prerequisites
- Port an existing stable Sandbox app to the SDK 1.0 preview `@next` line.
Permissions
- Changes packages, image, and process/terminal/interpreter APIs; production cutover can interrupt work.
Limitations
Worker and image must share @next; production needs explicit approval and immediate rollout; bridge stays stable.
Pinned upstream source
- Repository
- cloudflare/skills
- File path
- skills/sandbox-migrate-to-next/SKILL.md
- Pinned commit
53395984c3ea1925d00fce03b266112302f050e6- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Compatible tools
@cloudflare/sandbox stable and @next · Sandbox migrate docs · Wrangler container rollout
Main topic
Take a coding Agent change from context to verification