Description
Description
When using Cloud API (NVIDIA Endpoints) as the inference provider, `nemoclaw status` displays "NIM: not running" at the bottom of the output. This is misleading because NIM is not applicable in Cloud API mode — no local NIM container is expected. The message implies a component is broken when it is simply not relevant to the current configuration.
Environment
Device: MacBook Pro M4
OS: macOS 26.0.1 (Darwin 25.0.0, arm64)
Architecture: arm64
Node.js: v22.22.1
npm: 10.9.4
Docker: Docker 29.2.1
OpenShell CLI: openshell 0.0.36
NemoClaw: v0.0.28
OpenClaw: 2026.4.9 (0512059)
Steps to Reproduce
1. Install NemoClaw v0.0.28
2. Onboard a sandbox with Cloud API provider (NVIDIA Endpoints):
nemoclaw onboard --non-interactive
(with NEMOCLAW_PROVIDER=build, NVIDIA_API_KEY set)
3. Run: nemoclaw my-assistant status
4. Observe the NIM field at the bottom of the output
Expected Result
When using Cloud API (remote inference), the NIM field should either:
a. Not be displayed at all (since NIM is not relevant), OR
b. Show "NIM: n/a (using Cloud API)" — clearly indicating this is expected, not an error
Actual Result
Status output shows at the bottom:
OpenClaw: running
NIM: not running
"NIM: not running" implies something is broken when it is the expected state for cloud inference.
Logs
Full status output confirms Cloud API configuration:
Provider: nvidia-prod
Inference: healthy (https://integrate.api.nvidia.com/v1/models)
Related test case: T5883724
Bug Details
| Field |
Value |
| Priority |
Unprioritized |
| Action |
Dev - Open - To fix |
| Disposition |
Open issue |
| Module |
Machine Learning - NemoClaw |
| Keyword |
NemoClaw, NemoClaw_CLI&UX, NEMOCLAW_GH_SYNC_APPROVAL, NemoClaw_Inference |
[NVB#6122160]
Description
Description
Environment Steps to Reproduce Expected Result Actual ResultStatus output shows at the bottom: OpenClaw: running NIM: not running "NIM: not running" implies something is broken when it is the expected state for cloud inference.LogsBug Details
[NVB#6122160]