Execution environments

Choose an execution environment from the work it must perform and the files it must retain. A containerized HTTP service, an agent editing durable documents, and a task that installs dependencies and runs a repository's test suite have different requirements.

Choose an environment

Requirement	Capability	Dedicated page
An existing containerized service or custom Linux image	Containers with a Worker-facing Durable Object	Containers
Linux binaries, package installation, or an existing toolchain	Container execution through Sandbox	Sandbox
Generated JavaScript composing application tools	Dynamic Worker execution with supplied providers	Code Mode
A durable filesystem with a choice of command backends	Computer workspace	Computer
Structured file operations exposed to generated code	Shell workspace and state tools	Shell

Keep work across runs

Use workspace storage for files that should remain available to the same application identity. Use Artifacts when the work needs a Git history and a remote that other agents or tools can access. Use Sandbox backups to reuse a prepared directory in a later execution environment.

Those choices can be combined. A coding agent can clone an Artifacts repository into a sandbox, use a backup to avoid reinstalling unchanged dependencies, and publish its changes as a new commit.

Examples from the original page

• Code Runner
• Workspace Files
• Notebook
• Test Runner
• Text Search
• Team Repositories — Artifacts

Library Table

Library	Dedicated documentation
Runtime.Containers	Containers
Runtime.Sandbox, Runtime.SandboxBridge	Sandbox
Runtime.Computer	Computer workspaces
Runtime.ComputerArtifacts	Artifacts

Related Pages

• Agents & Tools overview
• Git tools
• Worker deployment

NuGet packages

Runtime.Computer 0.1.0, Runtime.ComputerArtifacts 0.1.0, Runtime.Containers 0.1.0, Runtime.Sandbox 0.1.0, Runtime.SandboxBridge 0.1.0.

See installation and release availability.