Sandbox CLI
Manage Docker-based sandbox containers for isolated agent execution.Overview
OpenClaw can run agents in isolated Docker containers for security. Thesandbox commands help you manage these containers, especially after updates or
configuration changes.
Commands
openclaw sandbox explain
Inspect the effective sandbox mode/scope/workspace access, sandbox
tool policy,
and elevated gates (with fix-it config key paths).
openclaw sandbox list
List all sandbox containers with their status and configuration.
- 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
openclaw sandbox recreate
Remove sandbox containers to force recreation with updated images/config.
--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
Use Cases
After updating Docker images
After changing sandbox configuration
After changing setupCommand
For a specific agent only
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
openclaw sandbox recreate to force
removal of old
containers. They’ll be recreated automatically with current settings when next needed.
Tip: prefer openclaw sandbox recreate over manual
docker rm. It uses
the Gateway’s container naming and avoids mismatches when scope/session keys change.
Configuration
Sandbox settings live in~/.openclaw/openclaw.json under
agents.defaults.sandbox (per-agent overrides go in
agents.list[].sandbox):
See Also
- Sandbox Documentation
- Agent Configuration
- Doctor Command - Check sandbox setup