Commands
openclaw sandbox list
List sandbox runtimes with status, backend, config match, age, idle time, and associated session/agent.
openclaw sandbox recreate
Remove sandbox runtimes to force recreation with current config. Runtimes are recreated automatically the next time the agent is used.
--all: recreate all sandbox containers--session <key>: recreate the runtime with this exact scope key (as shown bysandbox list); no short-name expansion--agent <id>: recreate runtimes for one agent (matchesagent:<id>andagent:<id>:*)--browser: only affect browser containers--force: skip the confirmation prompt
--all, --session, or --agent.
For ssh and OpenShell remote, recreate matters more than with Docker: the remote workspace is canonical after the initial seed, recreate deletes that canonical remote workspace for the selected scope, and the next run reseeds it from the current local workspace.
openclaw sandbox explain
Inspect the effective sandbox mode/scope/workspace access, sandbox tool policy, and elevated-tool gates (with fix-it config key paths).
The report keeps workspaceRoot as the configured sandbox root and separately shows the effective host workspace, backend runtime workdir, and Docker mount table. For workspaceAccess: "rw", the effective host workspace is the agent workspace rather than a directory below workspaceRoot.
recreate --session, this accepts short session names (for example main) and expands them against the resolved agent.
Why recreate is needed
Updating sandbox config does not affect running containers: existing runtimes keep their old settings, and idle runtimes are only pruned afterprune.idleHours (default 24h). Regularly used agents can keep stale runtimes alive indefinitely. openclaw sandbox recreate removes the old runtime so the next use rebuilds it from current config.
Common triggers
| Change | Command |
|---|---|
Docker image update (agents.defaults.sandbox.docker.image) | openclaw sandbox recreate --all |
Sandbox config (agents.defaults.sandbox.*) | openclaw sandbox recreate --all |
SSH target/auth (agents.defaults.sandbox.ssh.{target,workspaceRoot,identityFile,certificateFile,knownHostsFile,identityData,certificateData,knownHostsData}) | openclaw sandbox recreate --all |
OpenShell source/policy/mode (plugins.entries.openshell.config.{from,mode,policy}) | openclaw sandbox recreate --all |
setupCommand | openclaw sandbox recreate --all (or --agent <id> for one agent) |
Runtimes are automatically recreated when the agent is next used.
Registry migration
Sandbox runtime metadata lives in the shared SQLite state database. Older installs may have legacy registry files that regular reads no longer rewrite:~/.openclaw/sandbox/containers.json~/.openclaw/sandbox/browsers.json- one JSON shard per container/browser under
~/.openclaw/sandbox/containers/or~/.openclaw/sandbox/browsers/
openclaw doctor --fix to migrate valid legacy entries into SQLite. Invalid legacy files are quarantined so a corrupt old registry cannot hide current runtime entries.
Configuration
Sandbox settings live in~/.openclaw/openclaw.json under agents.defaults.sandbox (per-agent overrides go in agents.list[].sandbox):
Related
- CLI reference
- Sandboxing
- Agent workspace
- Doctor: checks sandbox setup.