Sandbox CLI

Manage sandbox containers and inspect effective sandbox policy

Sandbox CLI

Manage Docker-based sandbox containers for isolated agent execution.

Overview

ThinkFleet can run agents in isolated Docker containers for security. The sandbox commands help you manage these containers, especially after updates or configuration changes.

Commands

`thinkfleetbot sandbox explain`

Inspect the effective sandbox mode/scope/workspace access, sandbox tool policy, and elevated gates (with fix-it config key paths).

thinkfleetbot sandbox explain
thinkfleetbot sandbox explain --session agent:main:main
thinkfleetbot sandbox explain --agent work
thinkfleetbot sandbox explain --json

`thinkfleetbot sandbox list`

List all sandbox containers with their status and configuration.

thinkfleetbot sandbox list
thinkfleetbot sandbox list --browser  # List only browser containers
thinkfleetbot sandbox list --json     # JSON output

Output 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

`thinkfleetbot sandbox recreate`

Remove sandbox containers to force recreation with updated images/config.

thinkfleetbot sandbox recreate --all                # Recreate all containers
thinkfleetbot sandbox recreate --session main       # Specific session
thinkfleetbot sandbox recreate --agent mybot        # Specific agent
thinkfleetbot sandbox recreate --browser            # Only browser containers
thinkfleetbot sandbox recreate --all --force        # Skip confirmation

Options:

--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

After updating Docker images

# Pull new image
docker pull thinkfleetbot-sandbox:latest
docker tag thinkfleetbot-sandbox:latest thinkfleetbot-sandbox:bookworm-slim

# Update config to use new image
# Edit config: agents.defaults.sandbox.docker.image (or agents.list[].sandbox.docker.image)

# Recreate containers
thinkfleetbot sandbox recreate --all

After changing sandbox configuration

# Edit config: agents.defaults.sandbox.* (or agents.list[].sandbox.*)

# Recreate to apply new config
thinkfleetbot sandbox recreate --all

After changing setupCommand

thinkfleetbot sandbox recreate --all
# or just one agent:
thinkfleetbot sandbox recreate --agent family

For a specific agent only

# Update only one agent's containers
thinkfleetbot sandbox recreate --agent alfred

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 thinkfleetbot sandbox recreate to force removal of old containers. They'll be recreated automatically with current settings when next needed.

Tip: prefer thinkfleetbot 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 ~/.thinkfleetbot/thinkfleetbot.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": "thinkfleetbot-sandbox:bookworm-slim",
          "containerPrefix": "thinkfleetbot-sbx-"
          // ... more Docker options
        },
        "prune": {
          "idleHours": 24,               // Auto-prune after 24h idle
          "maxAgeDays": 7                // Auto-prune after 7 days
        }
      }
    }
  }
}

Sandbox CLI

Sandbox CLI

Overview

Commands

`thinkfleetbot sandbox explain`

`thinkfleetbot sandbox list`

`thinkfleetbot sandbox recreate`

Use Cases

After updating Docker images

After changing sandbox configuration

After changing setupCommand

For a specific agent only

Why is this needed?

Configuration

See Also

On this page