Manage sandbox runtimes for isolated agent execution: Docker/Podman containers, SSH targets, or OpenShell backends.

apus agent exec preserves a sandbox selected by the inherited config or --config, including its execution routing. Without a configured sandbox, its defaults allow full Gateway-host execution and restrict filesystem tools to --cwd. --isolated and --auth-env-only skip config inheritance and use those defaults.

Commands

apus sandbox list

List sandbox runtimes with status, backend, config match, age, idle time, and associated session/agent.

For configured plugin-provided backends such as OpenShell, the CLI loads the owning backend plugin before checking live runtime status. Browser-only operations do not require backend plugin activation.

apus sandbox list
apus sandbox list --browser  # browser containers only
apus sandbox list --json

apus sandbox recreate

Remove sandbox runtimes to force recreation with current config. Runtimes are recreated automatically the next time the agent is used.

apus sandbox recreate --all
apus sandbox recreate --agent mybot        # includes agent:mybot:* sub-sessions
apus sandbox recreate --session "agent:main:main"
apus sandbox recreate --browser --all      # only browser containers
apus sandbox recreate --all --force        # skip confirmation

Options:

Pass exactly one of --all, --session, or --agent.

Recreation requires exclusive offline ownership of the selected state directory. If its Gateway is running, the command refuses before inspecting or removing runtimes. Stop the Gateway through its service owner, wait for ownership to release, then rerun the command. Offline ownership stays held through confirmation and accepted teardown; a starting Gateway waits until cleanup settles. --force does not bypass this ownership check.

See local state owner routing for owner discovery, refusal states, and compatibility boundaries.

Scoped recreation selects registry entries before inspecting their backends. An unrelated runtime on another Podman connection or an unavailable backend does not block --session or --agent. The selected runtime still requires its recorded target to be active and reachable; --force only skips the confirmation prompt. Browser-only recreation does not inspect regular sandbox runtimes.

When recorded Podman targets differ, an unscoped sandbox list can still fail its target check. Restore the affected runtime's original connection, use its known exact scope key with recreate --session, and review the preview before confirming. If you do not know the exact scope, keep the registry intact; do not guess a key, broaden to --all, or rewrite its recorded target to bypass validation.

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.

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

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

Unlike recreate --session, this accepts short session names (for example main) and expands them against the resolved agent. An explicit --agent is sufficient for multi-agent fleets with no implicit owner; sandbox explanation does not require or guess a default first.

Why recreate is needed

Updating sandbox config does not affect running containers: existing runtimes keep their old settings, and idle runtimes are only pruned after prune.idleHours (default 24h). Regularly used agents can keep stale runtimes alive indefinitely. apus sandbox recreate removes the old runtime so the next use rebuilds it from current config.

Prefer apus sandbox recreate over manual backend-specific cleanup. It uses the Gateway's runtime registry and avoids mismatches when scope or session keys change.

Common triggers

Run apus sandbox recreate --all after any of these changes:

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:

Run apus 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 ~/.apus/apus.json under agents.defaults.sandbox (per-agent overrides go in agents.entries.*.sandbox):

{
  "agents": {
    "defaults": {
      "sandbox": {
        "mode": "all", // off, non-main, all
        "backend": "docker", // docker, podman, ssh; openshell is plugin-provided
        "scope": "agent", // session, agent, shared
        "docker": {
          "image": "apus-sandbox:bookworm-slim",
          "containerPrefix": "apus-sbx-",
          // ... more Docker options
        },
        "prune": {
          "idleHours": 24, // auto-prune after 24h idle
          "maxAgeDays": 7, // auto-prune after 7 days
        },
      },
    },
  },
}

Related