Feature: CLI 2026

Power-user CLI.

Overview

The Nova CLI for 2026 brings shell-first ergonomics to operators. The discipline matches operator workflow rather than forcing UI clicks; every product surface is scriptable.

• Power-user CLI. Every product surface scriptable; the CLI is not a thin wrapper, it is the operator's front door.
• OAuth device-code flow. No long-lived API keys; modern security default that matches enterprise expectations.
• JSON output by default. Pipe-friendly; jq and downstream tooling work without flag-twiddling.
• Per-environment profiles. Dev, staging, prod profile selection; multi-account workflows supported out of the box.

The approach

The practical approach is OAuth-first, JSON-default, profile-driven. The team's discipline produces fast operator workflow with no surprises.

• nova login. OAuth device-code flow; pairs with the CLI to a browser tab; no API key paste.
• nova --output json. Pipe-friendly; the default; reformat with --output table for human reads.
• nova --profile prod. Per-environment profile selection; explicit, never accidental.
• nova alias. Custom command shortcuts; power users compose their own primitives.

Why this compounds

CLI discipline compounds. Each captured workflow grows the team's automation surface; the value matures over years, not weeks.

• Faster operator workflow. CLI replaces UI clicks; multi-step operations become one command, then a script.
• Better automation. CLI in scripts produces reproducible operations; the team's automation library grows.
• Better integration. CLI integrates with team tooling (Slack ops, runbooks, dashboards); composability is the win.
• Investigation discipline. Ad-hoc queries via CLI support investigation; institutional knowledge grows with use.