-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat(cli): add --json output for list and status commands #753
Copy link
Copy link
Closed
Labels
area: cliCommand line interface, flags, terminal UX, or outputCommand line interface, flags, terminal UX, or outputarea: installInstall, setup, prerequisites, or uninstall flowInstall, setup, prerequisites, or uninstall flowarea: onboardingOnboarding FSM, provider setup, sandbox launch, or first-run flowOnboarding FSM, provider setup, sandbox launch, or first-run flowplatform: dgx-sparkAffects DGX Spark hardware or workflowsAffects DGX Spark hardware or workflows
Metadata
Metadata
Assignees
Labels
area: cliCommand line interface, flags, terminal UX, or outputCommand line interface, flags, terminal UX, or outputarea: installInstall, setup, prerequisites, or uninstall flowInstall, setup, prerequisites, or uninstall flowarea: onboardingOnboarding FSM, provider setup, sandbox launch, or first-run flowOnboarding FSM, provider setup, sandbox launch, or first-run flowplatform: dgx-sparkAffects DGX Spark hardware or workflowsAffects DGX Spark hardware or workflows
Type
Fields
Give feedbackNo fields configured for Bug.
Problem
Operational commands only emit human-formatted output. That makes automation, scripting, and debugging harder than necessary.
Scope
Add
--jsonoutput to:nemoclaw listnemoclaw statusnemoclaw <name> statusnemoclaw <name> policy-listAcceptance Criteria
--jsonContext
This came out of a CLI review against https://clig.dev/. Structured output is the clearest machine-friendliness gap in the current CLI.