Description

nemoclaw onboard cancelled via Ctrl+C at the Policy presets screen (step [8/8]) exits but leaves a fully created sandbox container running and registered as the default sandbox in nemoclaw list. The cancellation does not roll back or mark the sandbox as incomplete.

Environment

Device:        Ubuntu 24.04 server
OS:            Ubuntu 24.04
Architecture:  x86_64
Node.js:       v22.22.3
npm:           10.9.8
Docker:        Docker version 29.2.1, build a5c7197
OpenShell CLI: openshell 0.0.44
NemoClaw:      nemoclaw v0.0.55
OpenClaw:      OpenClaw 2026.5.22 (a374c3a)

Steps to Reproduce

1. Ensure Docker is running and nemoclaw and openshell CLIs are installed.
2. Run nemoclaw onboard.
3. Complete preflight, select NVIDIA Endpoints as the provider, configure NVIDIA API key, and choose model nvidia/nemotron-3-super-120b-a12b.
4. Accept defaults through messaging channels and resource profiles until sandbox creation starts.
5. Wait for the sandbox image build to complete and for NemoClaw to report ✓ Sandbox 'new-sb' created, dashboard live, and OpenClaw gateway launched inside the sandbox.
6. At step [8/8] Policy presets, when the Policy tier TUI is shown (Restricted / Balanced / Open), press Ctrl+C to cancel onboarding.
7. On the host, run docker ps | grep openshell.
8. Run nemoclaw list.

Expected Result

• nemoclaw onboard exits immediately with a non-zero exit code on Ctrl+C at the Policy presets screen.
• No new sandbox should be registered as default in NemoClaw when Policy presets were never confirmed.
• No orphaned OpenShell sandbox container should remain running from the cancelled onboarding attempt — either the container is cleaned up, or the sandbox is clearly marked as incomplete/unregistered.

Actual Result

nemoclaw onboard exits after Ctrl+C at the Policy presets TUI without clearly indicating a rollback or cleanup.

docker ps | grep openshell shows a running sandbox container created by the aborted onboarding, for example:

a0fdce402ec2  openshell/sandbox-from:1780333627  "/opt/openshell/bin/…"  23 seconds ago  Up 23 seconds (health: starting)  openshell-new-sb-32da96b7-88fb-4106-a52e-6ce1219acbd8

nemoclaw list shows the sandbox as fully registered and marked as the default, even though Policy presets were never applied:

Sandboxes:
  new-sb *
    agent:     openclaw
    model:     nvidia/nemotron-3-super-120b-a12b
    provider:  nvidia-prod
    CPU sandbox
    policies:  none
    dashboard: http://127.0.0.1:18789/

* = default sandbox

This leaves a partially configured sandbox treated as a valid default environment after a user-cancelled onboarding at the final policy step.

Logs

Not captured.

(docker ps and nemoclaw list output above are the primary evidence.)

Notes

• Title uses [All Platforms] because the issue is in nemoclaw onboard's Ctrl+C handling at Policy presets and is likely platform-agnostic. Behavior was directly reproduced on Ubuntu 24.04 with NemoClaw v0.0.55. Single-platform evidence — narrow to [Ubuntu 24.04] if QE confirms macOS/Spark behave differently.
• Related (not duplicate): [Ubuntu 24.04][Onboard] typing exit at inference provider selection does not cancel onboarding #4514 — typing exit at inference provider selection also fails to cancel onboarding cleanly. Same family of cancellation-handling bugs, different trigger.