Skip to content

[All Platforms] A sandbox named after a global command (e.g., "status", "list", "debug") becomes inaccessible because global commands take routing priority #1731

@zNeill

Description

@zNeill

Description

[Environment]
Device: Linux 5.15.0-171-generic x86_64, No GPU
NemoClaw: v0.0.11

[Steps to Reproduce]
If a user names their sandbox "status": nemoclaw status connect would try global "status" command, not sandbox "status"

[Expected Result]
Onboard should reject sandbox names that match global commands (status, list, debug, start, stop, onboard, setup, deploy, uninstall, credentials, help).

[Actual Result]
Names like "status" pass validation (matches /^a-z?$/) and would be registered, but nemoclaw status connect routes to the global status command.
Tested: nemoclaw onboard status → "Unknown onboard option(s): status" (treats "onboard" as global cmd, "status" as arg)
Tested: nemoclaw list status → shows sandbox list (treats "list" as global cmd, ignores "status")

Bug Details

Field Value
Priority Unprioritized
Action Dev - Open - To fix
Disposition Open issue
Module Machine Learning - NemoClaw
Keyword NemoClaw, NEMOCLAW_GH_SYNC_APPROVAL

[NVB# 6065943]

[NVB#6065943]

Metadata

Metadata

Assignees

No one assigned

    Labels

    NV QABugs found by the NVIDIA QA Teamarea: cliCommand line interface, flags, terminal UX, or output

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions