Sandbox CLI
Sandbox CLI
Section titled “Sandbox CLI”Manage Docker-based sandbox containers for isolated agent execution.
Overview
Section titled “Overview”BuilderForce Agents can run agents in isolated Docker containers for security. The sandbox commands help you manage these containers, especially after updates or configuration changes.
Commands
Section titled “Commands”builderforce sandbox explain
Section titled “builderforce sandbox explain”Inspect the effective sandbox mode/scope/workspace access, sandbox tool policy, and elevated gates (with fix-it config key paths).
builderforce sandbox explainbuilderforce sandbox explain --session agent:main:mainbuilderforce sandbox explain --agent workbuilderforce sandbox explain --jsonbuilderforce sandbox list
Section titled “builderforce sandbox list”List all sandbox containers with their status and configuration.
builderforce sandbox listbuilderforce sandbox list --browser # List only browser containersbuilderforce sandbox list --json # JSON outputOutput includes:
- Container name and status (running/stopped)
- Docker image and whether it matches config
- Age (time since creation)
- Idle time (time since last use)
- Associated session/agent
builderforce sandbox recreate
Section titled “builderforce sandbox recreate”Remove sandbox containers to force recreation with updated images/config.
builderforce sandbox recreate --all # Recreate all containersbuilderforce sandbox recreate --session main # Specific sessionbuilderforce sandbox recreate --agent mybot # Specific agentbuilderforce sandbox recreate --browser # Only browser containersbuilderforce sandbox recreate --all --force # Skip confirmationOptions:
--all: Recreate all sandbox containers--session <key>: Recreate container for specific session--agent <id>: Recreate containers for specific agent--browser: Only recreate browser containers--force: Skip confirmation prompt
Important: Containers are automatically recreated when the agent is next used.
Use Cases
Section titled “Use Cases”After updating Docker images
Section titled “After updating Docker images”# Pull new imagedocker pull builderforce-sandbox:latestdocker tag builderforce-sandbox:latest builderforce-sandbox:bookworm-slim
# Update config to use new image# Edit config: agents.defaults.sandbox.docker.image (or agents.list[].sandbox.docker.image)
# Recreate containersbuilderforce sandbox recreate --allAfter changing sandbox configuration
Section titled “After changing sandbox configuration”# Edit config: agents.defaults.sandbox.* (or agents.list[].sandbox.*)
# Recreate to apply new configbuilderforce sandbox recreate --allAfter changing setupCommand
Section titled “After changing setupCommand”builderforce sandbox recreate --all# or just one agent:builderforce sandbox recreate --agent familyFor a specific agent only
Section titled “For a specific agent only”# Update only one agent's containersbuilderforce sandbox recreate --agent alfredWhy is this needed?
Section titled “Why is this needed?”Problem: When you update sandbox Docker images or configuration:
- Existing containers continue running with old settings
- Containers are only pruned after 24h of inactivity
- Regularly-used agents keep old containers running indefinitely
Solution: Use builderforce sandbox recreate to force removal of old containers. They’ll be recreated automatically with current settings when next needed.
Tip: prefer builderforce sandbox recreate over manual docker rm. It uses the
Gateway’s container naming and avoids mismatches when scope/session keys change.
Configuration
Section titled “Configuration”Sandbox settings live in ~/.builderforce/builderforce.json under agents.defaults.sandbox (per-agent overrides go in agents.list[].sandbox):
{ "agents": { "defaults": { "sandbox": { "mode": "all", // off, non-main, all "scope": "agent", // session, agent, shared "docker": { "image": "builderforce-sandbox:bookworm-slim", "containerPrefix": "builderforce-sbx-", // ... more Docker options }, "prune": { "idleHours": 24, // Auto-prune after 24h idle "maxAgeDays": 7, // Auto-prune after 7 days }, }, }, },}See Also
Section titled “See Also”- Sandbox Documentation
- Agent Configuration
- Doctor Command - Check sandbox setup