Skip to content

feat(cli): clarify global vs sandbox-scoped status in help and UX #754

@kjw3

Description

@kjw3

Problem

nemoclaw status and nemoclaw <name> status do very different things, but the CLI does not explain that model clearly enough. New users can easily confuse global service status with sandbox health status.

Scope

  • Clarify the distinction in top-level help
  • Add better remediation hints when users run the wrong form
  • Consider whether command descriptions or output headers should make the hierarchy more explicit

Acceptance Criteria

  • Top-level help explicitly explains global commands vs sandbox-targeted commands
  • status output clearly identifies whether it is global or sandbox-scoped
  • Wrong-form usage gives a concrete next step

Context

This came out of a CLI review against https://clig.dev/. The current command model is workable, but not taught clearly by the CLI itself.

Metadata

Metadata

Assignees

Labels

area: cliCommand line interface, flags, terminal UX, or outputarea: installInstall, setup, prerequisites, or uninstall flowarea: onboardingOnboarding FSM, provider setup, sandbox launch, or first-run flow
No fields configured for Enhancement.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions