[WSL2][CLI&UX] nemohermes status exits non-zero despite printing a fully healthy status report
- Dominant language
- TypeScript
- Stars
- 22.5k
- Forks
- 3.1k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 715
Description
## Description
`nemohermes status` prints a complete, healthy status report (phase Ready, inference healthy, harness/agent info, policy dump) with no visible error text anywhere in stdout or stderr, but the command still exits with code 1.
Platform scope: Reproduced on WSL2 (x86) only; other platforms not tested.
Regression: Unknown — earlier versions not tested.
## Environment
```text
Device: WSL2 x86_64 CI runner
OS: WSL2 (Ubuntu on Windows)
Architecture: x86_64
OpenShell CLI: 0.0.106
NemoClaw: v0.0.119
```
## Steps to Reproduce
1. Onboard a sandbox with the Hermes agent
2. Run `nemohermes status`
## Expected Result
When the printed status report shows no errors (Ready phase, healthy inference, etc.), the command should exit 0.
## Actual Result
Command exits 1 despite the full printed status report showing no errors:
```text
Active gateway set to 'nemoclaw'
Sandbox-scoped status for '':
Sandbox:
Model: nvidia/nemotron-3-super-120b-a12b
Provider: nvidia-prod
Inference: healthy (the sandbox inference route)
Inference (route reachability): reachable (the sandbox inference route)
Inference (upstream): healthy (the NVIDIA Endpoints upstream API)
Serving process (hermes agent gateway): not checked
Host GPU: yes
Sandbox GPU: enabled (auto) (CUDA verified)
OpenShell: 0.0.106 (docker)
Policies: pypi
Harness: Hermes Agent (gateway)
SSH sessions: none
Permissions: not configured (default mutable state)
Agent: Hermes Agent v0.19.0
Phase: Ready
```
## Logs
Not captured
Contributor guide
Assessment
This issue has not been assessed yet.