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. 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; only the container stops running.

Start it again later:

$nemo-deepagents <sandbox-name> start

NemoClaw restarts the container so the managed terminal runtime can run again. 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.