Description

Environment

• Openshell: 0.0.11
• nemoclaw: 0.1.0 (main: dbfd78c)
• OS: Ubuntu
• Container runtime: Docker CE
• GPU: Available
• Ollama: Installed
• Ollama models: None (ollama list is empty)
• NemoClaw install method: curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash

When the installer or onboarding flow is run a second time to create a new sandbox, NemoClaw may clean up the existing nemoclaw gateway session before starting the new one. This can remove the previously created sandbox from OpenShell, but the old sandbox entry remains in the local NemoClaw registry. As a result, nemoclaw list still shows the old sandbox, while nemoclaw connect fails with sandbox not found.

[Steps to reproduce]:

1. Start from a machine where Docker is running and NemoClaw can onboard successfully.
2. Run the installer and complete onboarding for a first sandbox, for example:
   • sandbox name: joyce-o
3. Verify the first sandbox works: nemoclaw list nemoclaw joyce-o connect
4. Exit the sandbox.
5. Run the installer again: curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
6. During the second onboarding, create a different sandbox name, for example:
   • joyce-cloud
7. Observe that onboarding prints: Cleaning up previous NemoClaw session... ✓ Previous session cleaned up
8. Complete onboarding for the second sandbox.
9. Run: nemoclaw list nemoclaw joyce-cloud connect nemoclaw joyce-o connect openshell sandbox list openshell sandbox get joyce-o

[Expected]

• The user should be explicitly warned that the previous NemoClaw session and its sandboxes will be destroyed, and Local registry state should remain consistent with the real OpenShell state
• A sandbox that no longer exists in OpenShell should not continue to appear in nemoclaw list

Steps to reproduce

none

[NVB#6001101]