Description

Create a sandbox with access to a host workspace for gemini.

The workspace path is mounted inside the sandbox at the same path as on the host. Additional workspaces can be provided as extra arguments. Append ":ro" to mount them read-only; a read-only argument may name a single file, which holds that one path out of reach inside a workspace the sandbox can otherwise write.

Omit the path to create a sandbox without a workspace bind mount: the agent then works in the container's own filesystem instead of on your files.

Use "sbx run --name SANDBOX" to attach to the agent after creation.

With --cloud: Create a cloud sandbox for gemini.

Cloud sandboxes have no host workspace, so no path follows the agent. Sizing comes from --cpus and --memory and must land on a billable shape; without them a cloud sandbox gets 2 CPUs and 4 GiB. A template named with -t / --template must already exist in the cloud registry.

Cloud sandboxes use cloud network policies. Host network and HTTP policies do not apply. Set cloud account defaults with "sbx --cloud policy init <allow-all|balanced|deny-all>".

Use "sbx --cloud run --name SANDBOX" to attach to the agent after creation: cloud needs the agent, since a name alone is not a unique handle.

Global options

Examples

# Create in the current directory
sbx create gemini .

# Create with a specific path
sbx create gemini /path/to/project

# Create with additional read-only workspaces
sbx create gemini . /path/to/docs:ro

# Create without a workspace bind mount
sbx create gemini

# Create a cloud sandbox for gemini
sbx --cloud create gemini

# Create a named cloud sandbox with a mixin baked in
sbx --cloud create --name my-project gemini --kit ./my-mixin/

# Create from a template that already exists in the cloud registry
sbx --cloud create -t TEMPLATE