> ## Documentation Index
> Fetch the complete documentation index at: https://docs.platform.nora.my/llms.txt
> Use this file to discover all available pages before exploring further.

# Global flags & env vars

> The flags every command accepts, and the environment variables the CLI reads.

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

| Flag               | Env var          | Description                                                         |
| ------------------ | ---------------- | ------------------------------------------------------------------- |
| `--base-url <url>` | `NORA_BASE_URL`  | Server origin. Default: `https://platform.nora.my`.                 |
| `--workspace <id>` | `NORA_TENANT`    | Override active workspace for this command.                         |
| `--flow <slug>`    | `NORA_FLOW`      | Override active Flow for this command.                              |
| `--json`           | —                | Emit output as JSON (where the command supports formatting choice). |
| `--quiet` / `-q`   | —                | Suppress status output; only prints result.                         |
| `--verbose` / `-v` | `NORA_LOG=debug` | Show request/response tracing.                                      |
| `-h`, `--help`     | —                | Print help for the current command.                                 |
| `--version`        | —                | Print CLI version.                                                  |

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

## Environment variables

Full list:

| Variable                     | Purpose                                                 |
| ---------------------------- | ------------------------------------------------------- |
| `NORA_TOKEN`                 | Auth token (personal or workspace). Skips `auth login`. |
| `NORA_BASE_URL`              | Server URL.                                             |
| `NORA_TENANT`                | Active workspace override.                              |
| `NORA_FLOW`                  | Active Flow override.                                   |
| `NORA_CONFIG_DIR`            | Config/credentials directory.                           |
| `NORA_LOG`                   | Log level: `error`, `warn`, `info`, `debug`, `trace`.   |
| `NORA_NO_COLOR`              | Set to any value to disable ANSI colors.                |
| `EDITOR`                     | Editor used by `agents edit`, `tools edit`, etc.        |
| `HTTPS_PROXY` / `HTTP_PROXY` | HTTP proxy for the CLI.                                 |

## 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:

```bash theme={null}
nora --help                # top-level commands
nora agents --help         # agents subcommands
nora agents update --help  # every flag on `agents update`
```

## Version

```bash theme={null}
nora --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:

```bash theme={null}
nora flows list --json | jq -r '.[].slug'
```

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:

```bash theme={null}
NORA_NO_COLOR=1 nora flows list
```

Or pipe to `cat` — colors auto-disable when output isn't a TTY.

## Debugging

If a command misbehaves, turn on verbose logging:

```bash theme={null}
nora --verbose flows publish support-agent
```

Or:

```bash theme={null}
NORA_LOG=debug nora flows publish support-agent
```

You'll see the full HTTP request/response including headers (with token redacted). Good for reporting server-side issues.