Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows sandbox-migrate-to-next

Sandbox Migrate To Next

Migrate Cloudflare Sandbox apps from stable @cloudflare/sandbox to @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-next for apps already on the preview.

41902 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Migrate Cloudflare Sandbox apps from stable @cloudflare/sandbox to @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-next for apps already on the preview.

When to use it

The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Migrate stable → Sandbox SDK 1.0 preview (`@next`); Workflow; Hard rules; Replacement map; Audit; Clarify (ask when needed). It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.

Migrate stable → Sandbox SDK 1.0 preview (`@next`)WorkflowHard rulesReplacement mapAuditClarify (ask when needed)UpgradePackage and imagePython: cloudflare/sandbox:next-pythonCode by areaDeploy cutoverValidate

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
sandbox-migrate-to-next
description
Migrate Cloudflare Sandbox apps from stable @cloudflare/sandbox to @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-next for apps already on the preview.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "sandbox-migrate-to-next" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-f56455c9e6c81c1f-Sandbox-Migrate-To-Next.html
Save it as .cursor/skills/sandbox-migrate-to-next/SKILL.md or .claude/skills/sandbox-migrate-to-next/SKILL.md and keep the frontmatter name and description exactly as-is.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/cloudflare/skills' --list

npx skills add 'https://github.com/cloudflare/skills' --skill 'sandbox-migrate-to-next'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: sandbox-migrate-to-next description: Migrate Cloudflare Sandbox apps from stable @cloudflare/sandbox to @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-next for apps already on the preview. --- # Migrate stable → Sandbox SDK 1.0 preview (`@next`) **Perform** the port. Follow the steps in order. Depth lives in docs—fetch the linked page when a step needs detail. Human guide: [Migrate](https://developers.cloudflare.com/sandbox/1-0-preview/migrate/) · [1.0 preview](https://developers.cloudflare.com/sandbox/1-0-preview/) **New projects** should start on `@next` (**`sandbox-next`**), not this skill. **Day-to-day stable work** → **`sandbox-stable`**. Deprecated-API cleanup **without** moving to `@next` → [2026 deprecation guide](https://developers.cloudflare.com/sandbox/guides/2026-deprecation/) first if needed. Existing apps should migrate **when you can**, so you are ready when 1.0 becomes the stable release. Do **not** force production cutover without the user agreeing. **Prefer installed `@next` types and the migrate doc over memory.** ## Workflow 1. **Review** hard rules and the replacement map 2. **Audit** the codebase; list hits and target shapes 3. **Clarify** with the user (cutover, bridge, Python image, unclear sites) 4. **Upgrade** package, image, and code 5. **Validate** Stop after any step that needs a user decision. ## Hard rules - Worker package and container image must be the **same** `@next` line. - Production cutover uses **immediate** container rollout. Stable and `@next` control protocols are incompatible both ways; gradual rollout leaves a broken mixed window. In-flight container work can stop. - After cutover, `await sandbox.exec(...)` means process **started**, not command **finished**. - Argv is as-is (no implicit shell). Shell syntax needs an explicit shell binary. - Process handles have **no stdin** → terminals for interactive input. - Observation `timeout` / `AbortSignal` cancel the **wait only**, not the process. - No single retry loop for every error. - Do not invent APIs (`gitCheckout` on core, process stdin, string-exec completion helper). - Self-deployed bridge stays on **stable** (not part of the preview line yet). ## Replacement map | Stable | `@next` | | ------ | ------- | | `SANDBOX_TRANSPORT` / `transport` / `setTransport` | Remove — RPC only | | `await sandbox.exec("cmd")` → buffered result | `await sandbox.exec(argv)` → handle, then `output` / waits | | `execStream` / `startProcess` | Same handle: `logs`, `waitFor*`, `kill` | | Default / named sessions | Gone — `cwd`/`env` per launch, or one shell script | | `sandbox.terminal(request)` / session terminal | `createTerminal` + `terminal.connect(request)` | | xterm `sessionId` | `terminalId` | | Interpreter methods on `Sandbox` | `withInterpreter` → `sandbox.interpreter.*` | | `gitCheckout` | argv `git` via `exec` | | String kill signals | Numeric only | | Files, mounts, backups, ports, tunnels, `proxyToSandbox` | Mostly unchanged (ignore session/transport bits on stable pages) | Depth: [Migrate](https://developers.cloudflare.com/sandbox/1-0-preview/migrate/) · after port, day-to-day → **`sandbox-next`** ## Audit ```sh rg 'SANDBOX_TRANSPORT|transport:|setTransport|enableDefaultSession|createSession|getSession|deleteSession|execStream\(|startProcess\(|killProcess\(|sandbox\.terminal\(|sessionId|gitCheckout\(|SandboxTransport|ExecutionSession' ``` Also: string `exec(`, `cd` then a later `exec`, bare `createCodeContext` / `runCode` on `Sandbox`. ## Clarify (ask when needed) - OK to cut production with `--containers-rollout=immediate` (live processes/terminals/streams may stop)? - Self-deployed bridge? Leave on stable. - Python interpreter → **`-python`** image variant? - Call sites not covered by the map? ## Upgrade ### Package and image ```sh npm install @cloudflare/sandbox@next ``` ```dockerfile FROM cloudflare/sandbox:next # Python: cloudflare/sandbox:next-python ``` Same prerelease tag on Worker and image when not on floating `next`. ### Code by area Apply replacements from the map. For each area, implement from the doc—not from stable habits: | Area | Doc | | ---- | --- | | Commands / handles / waits | [Processes](https://developers.cloudflare.com/sandbox/1-0-preview/processes/) · [Processes API](https://developers.cloudflare.com/sandbox/1-0-preview/api/processes/) | | `cwd` / `env` / secrets | [Environment](https://developers.cloudflare.com/sandbox/1-0-preview/environment/) · [Outbound traffic](https://developers.cloudflare.com/sandbox/guides/outbound-traffic/) | | Drop sessions | [Migrate](https://developers.cloudflare.com/sandbox/1-0-preview/migrate/) · [Lifecycle](https://developers.cloudflare.com/sandbox/1-0-preview/lifecycle/) | | Terminals | [Terminals](https://developers.cloudflare.com/sandbox/1-0-preview/terminals/) | | Interpreter | [Interpreter](https://developers.cloudflare.com/sandbox/1-0-preview/interpreter/) | | Errors | [Errors](https://developers.cloudflare.com/sandbox/1-0-preview/errors/) | | Durable job across requests | [Process execution — lifetime / durability](https://developers.cloudflare.com/sandbox/1-0-preview/processes/) | **Commands (shape):** ```ts // Before (stable) const result = await sandbox.exec("npm test"); // After (@next) const process = await sandbox.exec(["/bin/bash", "-lc", "npm test"]); const result = await process.output({ encoding: "utf8" }); ``` ```ts const server = await sandbox.exec(["/bin/bash", "-lc", "npm run dev"], { cwd: "/workspace/app", }); await server.waitForPort(3000, { timeout: 60_000 }); await server.kill(); // numeric; default 15 ``` **Terminals (shape):** ```ts const terminal = await sandbox.createTerminal({ command: ["bash"], cwd: "/workspace" }); const t = await sandbox.getTerminal(terminal.id); if (!t) return new Response("terminal gone", { status: 410 }); return t.connect(request, { cursor, cols, rows }); ``` **Interpreter (shape):** ```ts import { Sandbox as BaseSandbox } from "@cloudflare/sandbox"; import { withInterpreter } from "@cloudflare/sandbox/interpreter"; export class Sandbox extends BaseSandbox { interpreter = withInterpreter(this); } ``` **Git (shape):** ```ts const clone = await sandbox.exec( ["git", "clone", "--depth", "1", "--", repoUrl, "/workspace/repo"], { cwd: "/workspace" }, ); const result = await clone.output({ encoding: "utf8" }); ``` Delete transport settings entirely. Remove session APIs. Isolate users with **separate sandbox IDs**. ### Deploy cutover Staging/branch first. Production is **one** deploy of matching Worker + image: ```sh npx wrangler deploy --containers-rollout=immediate ``` Leave `rollout_active_grace_period` at default `0` (or set `0` if raised). After cutover, pre-deploy process/terminal IDs are invalid. Details: [Migrate](https://developers.cloudflare.com/sandbox/1-0-preview/migrate/) · [Container rollouts](https://developers.cloudflare.com/containers/platform-details/rollouts/) ## Validate 1. Lockfile + Dockerfile on the same `@next` line 2. Typecheck against `@next` 3. Smoke argv `exec` + `output({ encoding: "utf8" })` 4. Smoke long process / terminal / interpreter if used 5. Errors distinguished: unavailable / interrupted-RPC / stale / local wait 6. No live secrets in sandbox env 7. Grep again for removed APIs 8. Production used `--containers-rollout=immediate` Then day-to-day work uses **`sandbox-next`**. ## Red flags — stop and fix - Mixing `@next` Worker with stable image (or reverse) - Gradual container rollout for this cutover - Treating `await exec` as command completion - Assuming `cd` / exports persist across `exec` calls - One retry wrapper for every error - Inventing `gitCheckout`, process stdin, or undocumented APIs - Keeping pre-cutover process/terminal IDs after deploy - Forcing production cutover without user agreement - Putting live secrets in `setEnvVars` / launch `env`

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…