CLI Commands
Quick reference for all NNO CLI commands — auth, project, feature, and marketplace.
CLI Commands
Quick reference for the nno CLI. For detailed flags and exit codes, see /reference/cli.
Auth
| Command | Description | Key flags |
|---|---|---|
nno login | Authenticate with NNO | --token <token> for CI use |
nno logout | Clear stored credentials | — |
nno whoami | Show current auth status and platform | — |
nno login --token eyJ... # CI / non-interactive
nno whoami # → Authenticated as [email protected], Platform: k3m9p2xw7q
nno logoutProject
Commands for managing the console shell and platform services.
| Command | Description | Key flags |
|---|---|---|
nno project dev | Start all NNO services for local development | — |
nno project build | Build the console shell | -e, --env stg|prod |
nno project deploy <platformId> | Trigger a Cloudflare Pages deployment | --env dev|stg|prod |
nno project check | Validate project config for a target environment | -e, --env local|dev|stg|prod |
nno project dev # starts all 8 services concurrently
nno project build --env prod # builds console → apps/console/dist/
nno project deploy k3m9p2xw7q --env prod
nno project check --env stg # validates wrangler.toml, env vars, IDsnno project dev starts all backend services (IAM, Registry, Billing, Provisioning, Stack Registry, CLI Service, Gateway) plus the console frontend — colour-coded in your terminal.
nno project check runs a set of preflight checks (wrangler.toml present, environment sections defined, no placeholder IDs, required env vars set) and exits with code 2 if any errors are found.
Feature
Commands for building and publishing NNO feature packages.
| Command | Description | Key flags |
|---|---|---|
nno feature init <name> | Scaffold a new feature package | --no-service, --dir <path> |
nno feature dev | Start the local feature dev environment | --no-service, --platform <id>, --env dev|stg |
nno feature build | Build the feature package | — |
nno feature test | Run feature tests | — |
nno feature validate | Check NNO compatibility | <path> (default: .) |
nno feature submit | Submit to NNO Marketplace | -m <message>, --private, --dry-run |
nno feature status | Check marketplace submission status | [submissionId] |
nno feature init my-analytics --no-service # UI-only feature, no Worker
nno feature dev # mock shell at localhost:5100
nno feature dev --platform k3m9p2xw7q # connect to real platform
nno feature validate # checks manifest, types, permissions
nno feature submit -m "Initial release"nno feature validate checks five rules: package.json exists, "neutrino": {"type": "feature"} is declared, featureManifest is exported, TypeScript compiles without errors, and permission keys follow the {featureId}:{action} format.
Marketplace
| Command | Description | Key flags |
|---|---|---|
nno marketplace list | Browse the feature catalogue | --type core|domain|client, --search <term> |
nno marketplace approve <id> | Approve a submission (NNO operators only) | — |
nno marketplace reject <id> | Reject a submission (NNO operators only) | --reason <text> |
nno marketplace list --search analytics
nno marketplace list --type domainMarketplace commands that interact with the NNO CLI Service (submit, approve, reject, status) require authentication (nno login) and the CLI Service to be running.
For the complete flag reference, exit codes, and advanced usage patterns, see CLI Reference.