# Niro in CI

**CI is a build machine with no person at it.** Niro's setup is built for a person at a terminal, so CI support is partial.

## What does not work without a person

- **`niro start` needs a terminal.** Without one it stops with "`niro start` is interactive and there is no terminal to prompt on."

- **Connecting agents needs a browser sign-in.** `niro mcp install` accepts only the browser sign-in that `niro start` does. After `niro login --api-key` it refuses with "Not signed in. Run niro login".

- **Sending the coverage audit.** The audit reads your plan through your `niro login` sign-in before it sends anything, so on a machine with no sign-in nothing is sent. Setting `NIRO_AUDIT_API_KEY` does not change that: the key only replaces the upload's own sign-in header. When the sign-in is missing, `niro audit-send` says so: "Nothing sent: not signed in. The audit reads your plan through your `niro login` sign-in, so run `niro login` first."

## What works

- **Confirming without a prompt.** `niro uninstall --yes` and `niro audit-push-repo --yes` skip their question. Without a terminal they need `--yes`, and refuse without it.

- **Signing in with a key from a pipe.** `niro login --api-key` reads the key from a pipe when there is no terminal. This way of signing in is due to be removed.

## Not yet established

Whether a key-based sign-in lets `niro build` and `niro ask` run on a build machine has not been tested. Treat Niro in CI as not supported until this page says otherwise.