cloudflare-sandbox

Cloudflare Sandboxes provide isolated Linux containers at the edge for secure code execution of untrusted scripts. Deploy sandboxes within Workers and Durable Objects, execute Python or Node.js code via the exec API, and destroy containers after use to eliminate attack surface.

Yes, sandboxes support session-based workflows for multi-step tasks. Create a session to maintain working directories and state across executions; use readFile, writeFile, and gitCheckout APIs within the same session, then destroy when complete.

Edge sandboxes enable ephemeral code execution for AI agent workflows and notebooks. Spin up per-request containers in Cloudflare's distributed network, execute generated code safely, and tear down automatically—ideal for AI-assisted tasks without persistent infrastructure.

Yes, sandboxes include gitCheckout in the API surface for cloning repositories into ephemeral containers. Combine with code execution to enable CI-like builds, automated git operations, and repository-driven workflows within isolated edge environments.

Sandboxes are designed for stateless, per-request execution. Persistence requires external storage integration; containers are destroyed on lifecycle completion, so plan for data export before sandbox termination if long-term retention is needed.