Description
Inside the OpenClaw TUI, typing /nemoclaw status does not show a real NemoClaw status response or subcommand help. Instead it prints a generic message:
NemoClaw: No operations performed yet. Run nemoclaw onboard to get started.
even though NemoClaw is already onboarded and a sandbox is running.
Component area: CLI&UX (slash commands in TUI) / Agent&Skills (integration between OpenClaw TUI and NemoClaw).
Environment
Platforms verified: WSL2 (Ubuntu 22.04 in WSL2 on Windows), DGX Spark, Ubuntu 26.04
openshell: 0.0.39
nemoclaw: v0.0.48
docker: 29.4.3
node: v22.22.3
npm: 10.9.8
OpenClaw: 2026.4.24 (cbcfdf6)
Steps to Reproduce
Pre-condition: NemoClaw has been successfully onboarded against any cloud provider, and at least one sandbox is running.
- On the host, connect to a running sandbox:
- Inside the sandbox shell, start the OpenClaw TUI:
- Inside the TUI input line, type the NemoClaw slash command and press Enter:
- Observe the TUI output.
Expected Result
Typing /nemoclaw inside the OpenClaw TUI should:
- Show autocomplete hints for available subcommands (for example,
status, logs, etc.).
Typing /nemoclaw status and pressing Enter should:
- Return inline status output in the TUI, reflecting the current NemoClaw/sandbox state (e.g., provider, sandbox health).
A silent no-op, a missing autocomplete hint, or a generic "no operations" banner in place of real status is considered a FAIL.
Actual Result
After typing /nemoclaw status and pressing Enter, the TUI shows:
/nemoclaw status
NemoClaw: No operations performed yet. Run nemoclaw onboard to get started.
There is:
- No autocomplete for
/nemoclaw subcommands.
- No structured status information about the running NemoClaw instance or sandbox.
- A misleading suggestion to "Run
nemoclaw onboard" despite NemoClaw already being onboarded and in use.
Logs
No explicit error is printed to the terminal outside the TUI. The only observable behavior is the TUI content shown in Actual Result above.
Description
Inside the OpenClaw TUI, typing
/nemoclaw statusdoes not show a real NemoClaw status response or subcommand help. Instead it prints a generic message:even though NemoClaw is already onboarded and a sandbox is running.
Component area: CLI&UX (slash commands in TUI) / Agent&Skills (integration between OpenClaw TUI and NemoClaw).
Environment
Steps to Reproduce
Pre-condition: NemoClaw has been successfully onboarded against any cloud provider, and at least one sandbox is running.
Expected Result
Typing
/nemoclawinside the OpenClaw TUI should:status,logs, etc.).Typing
/nemoclaw statusand pressing Enter should:A silent no-op, a missing autocomplete hint, or a generic "no operations" banner in place of real status is considered a FAIL.
Actual Result
After typing
/nemoclaw statusand pressing Enter, the TUI shows:There is:
/nemoclawsubcommands.nemoclaw onboard" despite NemoClaw already being onboarded and in use.Logs
No explicit error is printed to the terminal outside the TUI. The only observable behavior is the TUI content shown in Actual Result above.