CLI Overview¶
nsx is the primary interface for the NSX app lifecycle.
Current top-level commands:
addboardbuildcachecleancommandsconfigurecreate-appdoctorflashlist-moduleslockmodulenewoutdatedprobesresetsbomsyncupdateview
add, list-modules, and new are convenience aliases. Run
nsx commands for the categorized command graph and workflow hints.
Typical Lifecycle¶
- run
doctorif the local toolchain or SEGGER environment looks suspect - create an app
- configure the app
- build the app
- flash and view output
- add or remove modules as needed
App Directory Resolution¶
Most NSX commands operate on an app directory containing nsx.yml.
- If you run a command from the app root, you can usually omit
--app-dir. - If you run a command from a subdirectory inside the app, NSX walks upward
until it finds the nearest
nsx.yml. - The upward search stops at the filesystem root or a Git repository boundary.
- Use
--app-dirwhen you want to target a different app explicitly.
Agent-Friendly Discovery¶
For LLM and agent workflows, prefer the CLI discovery surfaces over scraping table output or general help text:
nsx commands --jsonfor the command tree, arguments, and workflow hintsnsx module list --registry-only --jsonfor catalog discoverynsx module describe <module> --jsonfor per-module metadata
Use the task-oriented pages in User Guide when you want workflow help. Use this section when you want exact command syntax.
The JSON command graph is the authoritative machine-readable syntax source.
Reference pages summarize common options, so automation should consume
nsx commands --json instead of copying usage text from documentation.