Description

Synopsis: [NemoClaw][Jetson][Sandbox] nemoclaw onboard --dangerously-skip-permissions creates sandbox but does not register it in CLI — sandbox unmanageable

Keywords: NemoClaw, NEMOCLAW_GH_SYNC_APPROVAL, NemoClaw_Sandbox, NemoClaw_Security

Severity: 2-Different from Spec

Description:

[Issue Summary]

When creating a second sandbox with --dangerously-skip-permissions, the sandbox is created in OpenShell but NOT registered in NemoClaw CLI. User has an orphaned sandbox they cannot manage, inspect, or destroy through CLI.

[Environment]

Device: Jetson (dl20g11-1007)
OS: Ubuntu 24.04 (x86_64)
Node.js: v22.22.2
Docker: Docker Engine 29.1.3
OpenShell CLI: 0.0.26
NemoClaw: v0.0.21
OpenClaw: 2026.4.2

[Steps to Reproduce]

1. nemoclaw onboard (create first sandbox "test21")
2. CHAT_UI_URL=http://127.0.0.1:18790 nemoclaw onboard --dangerously-skip-permissions --non-interactive --yes-i-accept-third-party-software
3. Onboard completes successfully
4. nemoclaw list → only shows test21
5. nemoclaw skiptest status → "Unknown command"

[Expected Behavior]

nemoclaw list shows both sandboxes. nemoclaw skiptest status works.

[Actual Behavior]

Second sandbox is running and functional (openshell sandbox exec works, inference works) but invisible to NemoClaw CLI. Only recoverable via raw openshell commands.

[Suspected Root Cause / Notes]

Sandbox registration in NemoClaw CLI may fail silently or be skipped when --dangerously-skip-permissions is used with a second sandbox.

[Regression?]

Unknown

Bug Details

[NVB#6100043]