Docs · Platform
How Sandboxes works
The life of a hosted task.
1A fresh sandbox starts
Each hosted session gets its own sandbox from an image pinned by digest.
2Traffic goes through a gateway
A per-sandbox gateway blocks internal and cloud metadata addresses.
3Credentials stay outside
The host holds secrets and never copies them into the sandbox.
4Torn down when the work ends
The sandbox is released when the turn finishes; output, decisions, and useful procedures stay in your company layer.
Isolation for hosted and local work
- gVisor isolation
- Hosted tools run inside gVisor, a user-space kernel between the agent and the host.
- Clean environments
- Shell environments are scrubbed, so host credentials do not leak into commands.
- Guardrails in Deixic Code
- On your machine an action firewall and approvals gate risky commands, and you can turn on the macOS or Linux sandbox.