Description

Description

Template 5987908 validates recovery when the local registry and live container state diverge. On vm4 with NemoClaw v0.0.53, the CLI first suggested rebuild --yes, but connect removed the stale local registry entry before rebuild could run, leaving no usable recovery path.

Environment

Device: NVIDIA A100-SXM4-40GB VM
OS: Ubuntu 24.04.4 LTS
Architecture: x86_64
Node.js: command not found on host
npm: command not found on host
Docker: Docker version 29.5.2, build 79eb04c
OpenShell CLI: openshell 0.0.44
NemoClaw: nemoclaw v0.0.53
OpenClaw: OpenClaw v2026.5.22 (from nemoclaw my-assistant status)Steps to Reproduce

1. Create a throwaway sandbox by restoring a snapshot into div-vm4-121836.
2. Confirm a marker file exists in the throwaway sandbox.
3. Remove the throwaway sandbox Docker container outside NemoClaw.
4. Run nemoclaw list.
5. Run nemoclaw div-vm4-121836 status.
6. Run nemoclaw div-vm4-121836 connect.
7. Follow the earlier recovery hint and run nemoclaw div-vm4-121836 rebuild --yes.Expected Result

The CLI should provide one consistent recovery path. If status recommends rebuild --yes, a subsequent recovery command should still be able to rebuild/recreate the sandbox and preserve workspace state, or the CLI should not delete the registry state needed for that recovery.Actual Result

list still showed the stale sandbox. status reported the sandbox was stuck in Provisioning and recommended rebuild:

Sandbox 'div-vm4-121836' is stuck in 'Provisioning' phase.
Run nemoclaw div-vm4-121836 rebuild --yes to recreate the sandbox

Then connect removed the local registry entry:

Sandbox 'div-vm4-121836' is not present in the live OpenShell gateway.
Removed stale local registry entry.

After that, rebuild could not run:

Sandbox 'div-vm4-121836' does not exist.
Registered sandboxes: my-assistant

Bug Details

[NVB#6239911]