Description

When i rebooted the ubuntu machine i have to manually do "nemoclaw <> connect" for the gateway to come online for which there is already a issue created. When i tried to stop the gateway using "openshell gateway stop" and "openshell gateway start" it removed the sandbox itself

Reproduction Steps

run 'openshell gateway stop'
openshell gateway start ### this starts the process without any error

###########
✓ Checking Docker
✓ Checking Docker
✓ Checking Docker
✓ Checking Docker
✓ Downloading gateway
✓ Initializing environment
✓ Starting gateway
✓ Gateway ready

Name: openshell
Endpoint: https://127.0.0.1:8080

✓ Active gateway set to 'openshell'
#############

But when i do nemoclaw connect

Sandbox '<>' is not present in the live OpenShell gateway.
Removed stale local registry entry.
Run nemoclaw list to confirm the remaining sandboxes, or nemoclaw onboard to create a new one.

########

With this I have to recreated the sandbox and it was able to pickup just the telegram configuration etc... but not the telegram userid.

Environment

Docker version 29.4.1, build 055a478
Distributor ID: Ubuntu
Release: 24.04
Codename: noble
nemoclaw v0.0.21
openshell 0.0.26

Debug Output

nemoclaw list

  No sandboxes registered. Run `nemoclaw onboard` to get started.

nemoclaw <> connect
  Sandbox 'nttpg01' is not present in the live OpenShell gateway.
  Removed stale local registry entry.
  Run `nemoclaw list` to confirm the remaining sandboxes, or `nemoclaw onboard` to create a new one.

Logs

Checklist

• I confirmed this bug is reproducible
• I searched existing issues and this is not a duplicate