Cloudflare Sandbox
Cloudflare Sandbox uses @cloudflare/sandbox to provide a container-backed Linux environment to a Flue application deployed on Cloudflare. This integration is platform-native: it is not a connector module for a Node-target application.
Use the Cloudflare target
Cloudflare Sandbox requires a Worker deployment, Durable Object/container configuration, and a container image. Add the dependency to a Cloudflare-targeted project, declare the sandbox binding in Wrangler configuration, and pass the RPC stub returned by getSandbox(...) to an agent:
import { getSandbox } from '@cloudflare/sandbox';
import { createAgent } from '@flue/runtime';
type Env = { Sandbox: DurableObjectNamespace };
export default createAgent<unknown, Env>(({ id, env }) => ({
model: 'anthropic/claude-sonnet-4-6',
sandbox: getSandbox(env.Sandbox, id),
cwd: '/workspace',
}));
Requirements
| Requirement | Value |
|---|---|
| Target | Cloudflare only |
| Package | @cloudflare/sandbox |
| Platform configuration | Container image and Durable Object/container binding in Wrangler configuration |
| Environment | Linux container filesystem and command behavior |
| Lifecycle identity | Choose stable sandbox identity and retention appropriate to your application |
Choose this integration when
Use Cloudflare Sandbox when an agent on Cloudflare needs git, package installation, native binaries, or other Linux tooling. Prefer Cloudflare Shell instead when a durable workspace with Workspace-oriented operations is sufficient and a Linux toolchain is unnecessary.
Treat network egress, mounted data, credentials, and side effects as application security decisions. See Sandboxes and Deploy on Cloudflare.