NemoClaw provides no way to temporarily stop or pause a running sandbox. The only options are connect, exec, rebuild, destroy, and recover — there is no stop or pause subcommand. Users who want to free up resources without losing their workspace are forced to either leave the sandbox running or destroy it entirely. nemoclaw stop and nemoclaw start exist but only control the tunnel service (cloudflared), not the sandbox container.
Device: MacBook (KGMW04R4VX, Apple M4 Pro)
OS: macOS (Darwin 25.5.0, arm64)
Architecture: arm64
Node.js: v22.22.3
npm: 10.9.8
Docker: 29.5.2
OpenShell CLI: 0.0.44
NemoClaw: v0.0.69
OpenClaw: 2026.5.27
$ nemoclaw my-assistant stop
Unknown action: stop
Valid actions: agent, agents, channels, config, connect, dashboard-url, destroy,
doctor, download, exec, gateway-token, hosts-add, hosts-list, hosts-remove, logs,
policy-add, policy-explain, policy-list, policy-remove, rebuild, recover, sessions,
share, shields, skill, snapshot, status, upload
$ nemoclaw stop
Warning: Deprecated: 'nemoclaw stop' is now 'nemoclaw tunnel stop'.
(stops cloudflared tunnel only — sandbox container keeps running)
Description
NemoClaw provides no way to temporarily stop or pause a running sandbox. The only options are
connect,exec,rebuild,destroy, andrecover— there is nostoporpausesubcommand. Users who want to free up resources without losing their workspace are forced to either leave the sandbox running or destroy it entirely.nemoclaw stopandnemoclaw startexist but only control the tunnel service (cloudflared), not the sandbox container.Environment
Steps to Reproduce
nemoclaw onboard --name my-assistantnemoclaw my-assistant stopnemoclaw my-assistant --helpExpected Result
nemoclaw <name> stopstops the sandbox container (preserving workspace state).nemoclaw <name> startrestarts the stopped sandbox.Actual Result
NVB#6395457