[All Platforms][CLI&UX] 'nemoclaw inference set' does not redirect to openshell command (inconsistent with term/policy/gateway)

[PrachiShevate-nv]

Description

On Ubuntu 24.04 with NemoClaw v0.0.54, nemoclaw inference set behaves like a native NemoClaw command missing flags and never mentions OpenShell, while other host-level operations (term, policy set, gateway stop) correctly fail with "This operation belongs to OpenShell" and show the corresponding openshell command. This makes inference set inconsistent with the expected UX contract for OpenShell-owned operations.

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: v0.0.54
• OpenClaw: OpenClaw 2026.5.22 (a374c3a)

Steps to Reproduce

1. Verify NemoClaw CLI is installed and on PATH:

   nemoclaw --version

2. Ensure at least one sandbox exists and is healthy:

   nemoclaw onboard --name ollama-base
   nemoclaw ollama-base status

3. Run each of the following on the host:

   nemoclaw term            2>&1; echo "EXIT:$?"
   nemoclaw policy set      2>&1; echo "EXIT:$?"
   nemoclaw gateway stop    2>&1; echo "EXIT:$?"
   nemoclaw inference set   2>&1; echo "EXIT:$?"

4. For each command, check whether the output mentions openshell:

   nemoclaw term          2>&1 | grep -c 'openshell'
   nemoclaw policy set    2>&1 | grep -c 'openshell'
   nemoclaw gateway stop  2>&1 | grep -c 'openshell'
   nemoclaw inference set 2>&1 | grep -c 'openshell'

Expected Result

All four commands (term, policy set, gateway stop, inference set) exit non-zero when invoked as nemoclaw <openshell-op>.

Each prints a message stating the operation belongs to OpenShell and includes at least one example openshell command, for example:

• nemoclaw term → "This operation belongs to OpenShell. Run: openshell term"
• nemoclaw inference set → "This operation belongs to OpenShell. Run: openshell inference set -g nemoclaw --model <model> --provider <provider>"
• nemoclaw policy set → "Run: openshell policy set --policy <policy-file> <sandbox-name>"
• nemoclaw gateway stop → "Run: openshell gateway stop -g nemoclaw"

For all four commands, nemoclaw <op> 2>&1 | grep -c 'openshell' returns >= 1.

Actual Result

nemoclaw term:

Unknown nemoclaw command: term
This operation belongs to OpenShell.
Run: openshell term
Use this to monitor gateway logs and policy approval prompts.
Run 'nemoclaw help' for NemoClaw commands.
EXIT:1

grep -c 'openshell' → 1

nemoclaw policy set:

Unknown nemoclaw command: policy set
This operation belongs to OpenShell.
Run: openshell policy set --policy <policy-file> <sandbox-name>
For NemoClaw presets, use: nemoclaw <sandbox-name> policy-add <preset>
Run 'nemoclaw help' for NemoClaw commands.
EXIT:1

grep -c 'openshell' → 1

nemoclaw gateway stop:

Unknown nemoclaw command: gateway stop
This operation belongs to OpenShell.
Run: openshell gateway stop -g nemoclaw
Run 'nemoclaw help' for NemoClaw commands.
EXIT:1

grep -c 'openshell' → 1

nemoclaw inference set ← INCONSISTENT:

 › Error: The following errors occurred:
 ›   Missing required flag model
 ›   Missing required flag provider
 ›   See more help with --help
EXIT:2

grep -c 'openshell' → 0

For term, policy set, and gateway stop, behavior matches the expected OpenShell redirection: non-zero exit, clear "belongs to OpenShell" message, and an example openshell command.

For inference set, the CLI treats the command as a NemoClaw-native command with missing flags, never mentions OpenShell, and provides no openshell inference set guidance, so the user cannot easily discover the correct OpenShell command from this error.

Logs

CLI output is included above under Actual Result.
Additional logs (gateway or sandbox logs) were not captured for this UX-only issue.