Manage SandboxesOperate Sandboxes

Run Sandboxes

View as Markdown

Use these workflows to keep existing sandboxes reachable and control the resources they consume.

Run Multiple Sandboxes

Deep Agents sandboxes do not expose a dashboard port. The first nemo-deepagents onboard run can use the default sandbox name from the wizard. When you create another Deep Agents sandbox, choose a distinct sandbox name in the wizard or pass --name in scripted runs.

If you intentionally run separate OpenShell gateways on the same host, set a different NEMOCLAW_GATEWAY_PORT before each onboarding run. NemoClaw isolates the gateway name and local state by port so one port-specific gateway does not replace another. A non-default NEMOCLAW_GATEWAY_PORT also gets its own host state root at ~/.nemoclaw/gateways/<port>/, with a separate sandbox registry, snapshots, and legacy credential-migration files, so gateway-scoped state stays segregated while shared host-level files remain under ~/.nemoclaw/. On first use after upgrading, NemoClaw moves legacy rows and related state only when their recorded gateway identity matches the selected port; ambiguous state is left untouched with remediation. Provider credentials remain in the OpenShell gateway store. The default port keeps the shared ~/.nemoclaw/ location. When other ports remain, nemo-deepagents uninstall removes only the selected gateway and keeps the shared CLI, services, images, providers, configuration, models, and swap. Gateway cleanup is scoped by sandbox name and port.

$nemo-deepagents onboard
$# For an additional named sandbox:
$nemo-deepagents onboard --name <sandbox-name>

Stop and Start a Sandbox

Stop a sandbox’s container to free CPU, memory, and GPU resources without losing anything:

$nemo-deepagents <sandbox-name> stop

Workspace files, credentials, network policies, and the registry entry are preserved. The container stops running.

Start it again later:

$nemo-deepagents <sandbox-name> start

After Docker reports the existing container as running, NemoClaw waits for OpenShell to report the sandbox in the Ready or Running state, then verifies the managed terminal runtime before the command reports success. Refer to nemo-deepagents <name> stop and nemo-deepagents <name> start for details. Use nemo-deepagents <name> destroy when you want to delete the sandbox instead.