Share feedback
Answers are generated based on the documentation.

sbx env

DescriptionManage sandboxes declaratively from an sbxenv.yaml file
Usagesbx env COMMAND

Experimental

This command is experimental.

Experimental features are intended for testing and feedback as their functionality or design may change between releases without warning or can be removed entirely in a future release.

Description

Manage a sandbox declared in an sbxenv.yaml file. The file selects the agent, kits, workspace mounts, environment variables, secrets, and credential bindings.

Use create to provision the sandbox, run to start or join its agent session, exec to run a command, and rm to remove it and its provisioned secrets. Use plan to preview changes. Changes require approval; --force skips the prompt.

Lifecycle commands and command-based secrets execute on the host with your permissions. Keep secret helpers and their dependencies outside writable sandbox mounts, and use absolute helper paths.

The environment file is mounted read-only by default when shared with the sandbox. Set sandboxOptions.writableEnvFiles only when you trust the agent to change what future invocations run on the host.

With --cloud, manage a cloud sandbox from the same file. Host workspace mounts, host port bindings, MCP definitions, registry credentials, and unsnapshotted dynamic secret sources are unsupported. Clone the project inside the sandbox instead.

Secrets and bindings are provisioned at creation; changes require recreating the sandbox. Removal deletes secrets provisioned by this environment; bindings are retained unless --prune-bindings is passed. Use the same cloud target, identity, and ordered files for subsequent commands.

For file syntax and workflows, see: https://docs.docker.com/ai/sandboxes/configuration/environment-files/

Commands

CommandDescription
sbx env createexperimental Create a sandbox environment from sbxenv.yaml
sbx env execexperimental Execute a command inside a sandbox environment
sbx env planexperimental Show what an environment would change outside the sandbox
sbx env rmexperimental Remove a sandbox environment and its scoped resources
sbx env runexperimental Create (if needed) and attach to a sandbox environment

Global options

OptionDefaultDescription
--cloudDispatch to Docker Cloud Sandboxes API instead of local sandboxd (supported by a growing set of verbs — run 'sbx --cloud --help' for the current list)
-D, --debugEnable debug logging