About my dockerfile
Application programming interfaces (APIs)
Authenticate to external services
Kits can attach credentials to outbound requests through the host-side proxy using a sentinel value.
Command-line interfaces (CLIs)
comment
Context scoping
Every query takes a Context argument scoping the request to an organization.
Control network access
Network rules define which domains the sandbox can reach or block; deny rules win over allow rules.
Credential bindings
Per-service mechanism and domain approval configured in credentials.yaml.
direc \
directive=value
directive=value1
directive=value2
Directory references
Use ${{ env.projectDir }} and ${{ env.fileDir }} to insert absolute host directory paths.
Dockerfile reference
Environment plan approval
sbx shows an environment plan and asks for approval before applying changes.
File formats
Format
Get started
Learn Docker basics and core concepts.
--gpu flag
Experimental flag enabling NVIDIA GPU passthrough for sandboxes.
Guides
Follow task-focused walkthroughs for common workflows.
imagePackagesForImageCoords
Fetches every package in an image, every CVE reported against it, and suppression status.
Inject files
Kits can inject static files bundled with the kit and setup.files written at startup with runtime values.
Interactive terminal dashboard
Running sbx with no subcommands opens a dashboard with live sandbox status, CPU and memory.
Manuals
Install, configure, and use Docker products.
MCP secrets
Secrets named with mcp: prefix are reserved for the host's MCP gateway.
Mixin kits
kind: mixin kits extend an existing agent with extra capabilities and can be stacked.
Mountless sandbox
OAuth passthrough
A kit can set OAuth passthrough: true to send the real token into the sandbox, reducing isolation.
Parser directives
Persistent skill store
Installed skills persist in a store that survives sandbox deletion.
Reference
Browse CLI, API, and file format documentation.
Registry credentials
Authentication for pulling images and kits via sbx secret set --registry.
Run commands
Kits can run install commands once at creation and startup commands each time the sandbox starts.
Sandbox environment files
Capture project setup in sbxenv.yaml to share agent, tools, resources, and credentials.
Sandbox kits
kind: sandbox kits define a full agent from scratch, including image, entrypoint, and network policies.
sbx cp
Transfers files between the sandbox and the host.
sbx create
Creates a sandbox in the background without attaching.
sbx exec
Runs commands or opens a shell inside a running sandbox.
sbx prune
Removes all stopped local sandboxes; running ones are never removed.
sbx run
Starts a sandbox, mounts a workspace, and attaches to the agent.
sbx secret set
Stores credentials injected by the host-side proxy without exposing them to the agent.
sbx secret set-custom
Stores a value keyed to a domain and environment variable for custom secrets.
Set environment variables
Environment variables set by the kit are available to the agent at runtime.
Shared agent skills
Install skills from Git repositories or import from supported agents on the host.
Sign and verify kits
Kits can be signed and verified, and signed kits can be required.
Skill access modes
Choose readonly, readwrite, or off mounts via --skills when creating a sandbox.
syntax=value
unknowndirective=value
User defaults
~/.sbxenv.yaml shares settings across projects; project settings override defaults.