Skip to main content
Certain flags are available on every nora subcommand. Everything they do can also be set with an environment variable — pick whichever fits your workflow.

Global flags

Precedence: flag > env var > active workspace/flow > CLI default.

Environment variables

Full list:

Precedence rules

Say you have:
  • NORA_TENANT=acme-prod in your shell.
  • nora auth workspaces current returns acme-dev.
  • You run nora --workspace acme-staging flows list.
The --workspace flag wins. This one command hits acme-staging. The env var and active workspace are unchanged. Same logic for --flow.

Getting help

--help is context-aware — the deeper you go, the more specific the help:

Version

Prints CLI version, target platform, and the build’s commit hash. Include this when filing bug reports.

Output formats

Most commands support two output modes:
  • Human (default) — colored tables and structured text.
  • JSON (--json) — parseable, pipe-friendly. Same data, no formatting.
Use --json for anything you’re piping to jq, another CLI, or a script. Example:
Some commands emit JSON by default (flows get, flows snapshot, agents sources list) because their content isn’t easily tabulated.

Colors

Colors are on by default when the CLI detects a TTY. Turn off:
Or pipe to cat — colors auto-disable when output isn’t a TTY.

Debugging

If a command misbehaves, turn on verbose logging:
Or:
You’ll see the full HTTP request/response including headers (with token redacted). Good for reporting server-side issues.