Skip to content

[All Platforms][CLI&UX] no command reprints the "OpenClaw is ready" connection block after onboarding #7473

Description

@hulynn

Description

After onboarding completes, NemoClaw shows a "Start chatting" block with the
dashboard URL, terminal connect command, and management commands. There is no
supported CLI command that reprints this block on demand. Users who dismiss or
scroll past it must piece together the information from verbose status output
or run dashboard-url --quiet for just the URL — neither reproduces the
concise ready block shown at the end of onboarding.

Platform scope: All Platforms — confirmed on WSL2 x86_64 (Ubuntu 24.04, two machines,
v0.0.92 and v0.0.93), macOS aarch64, and DGX Spark aarch64 (native Linux). Feature
has never existed on any tested platform.
Regression: No — feature has never existed (confirmed absent in v0.0.92 and v0.0.93).

Environment

Device:        Windows PC with NVIDIA RTX PRO 6000 Blackwell Server (97 GB)
OS:            Ubuntu 24.04.4 LTS (WSL2 under Windows)
Architecture:  x86_64
Node.js:       v22.23.1
npm:           10.9.8
Docker:        29.5.3
OpenShell CLI: 0.0.85
NemoClaw:      v0.0.93
OpenClaw:      2026.7.1 (2d2ddc4)

Steps to Reproduce

  1. Complete a NemoClaw onboard. At the end, the "Start chatting" block is shown:

    Start chatting
    
      Browser:
        http://127.0.0.1:18789/
    
      Terminal:
        nemoclaw my-assistant connect
        then run: openclaw tui
    
    Manage later
    
      Status:      nemoclaw my-assistant status
      Logs:        nemoclaw my-assistant logs --follow
      Model:       nemoclaw inference set --model {model} --provider {provider} --sandbox my-assistant
      Policies:    nemoclaw my-assistant policy-add
      Credentials: nemoclaw credentials reset {KEY} && nemoclaw onboard
    
  2. After onboarding, attempt to reprint this block by running any of the following:

    • nemoclaw my-assistant show-connection-info
    • nemoclaw my-assistant connect --probe-only
    • nemoclaw my-assistant recover
    • nemoclaw my-assistant start
    • nemoclaw my-assistant gateway restart
    • nemoclaw my-assistant status
    • nemoclaw my-assistant doctor

Expected Result

At least one supported command reprints the full "Start chatting" ready block,
including: dashboard Browser URL, Terminal connect command, and Manage later
management commands. The command should work without re-running onboard.

Actual Result

No command reprints the ready block. The closest alternatives:

nemoclaw my-assistant show-connection-info
→ Unknown action: show-connection-info

nemoclaw my-assistant connect --probe-only
→ Probe complete: OpenClaw gateway is running in 'my-assistant'.

nemoclaw my-assistant recover
→ Probe complete: OpenClaw gateway is running in 'my-assistant'.

nemoclaw my-assistant start (sandbox already running)
→ Sandbox 'my-assistant' is already running. … Probe complete.

nemoclaw my-assistant gateway restart
→ Gateway restarted; health passed; forwards checked/recovered for 'my-assistant'.

nemoclaw my-assistant status
→ Full health + policy dump (verbose, different format — does not show "Start chatting" block).

nemoclaw my-assistant doctor
→ Diagnostic [ok]/[fail]/[info] lines (diagnostic format, not ready block).

Valid sandbox actions in v0.0.93 (none reprints the ready block):
agent, agents, channels, config, connect, dashboard-url, destroy, doctor,
download, exec, gateway, gateway-token, hosts-add, hosts-list, hosts-remove,
inference, logs, mcp, policy-add, policy-explain, policy-get, policy-list,
policy-remove, rebuild, recover, sessions, share, shields, skill, snapshot,
start, status, stop, upload

Logs

Not captured — feature gap, not a runtime error.

Metadata

Metadata

Assignees

Labels

NV QABugs found by the NVIDIA QA TeamVDRLinked to VDR findingneeds: triageAwaiting maintainer classification

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions