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 startneeds a terminal. Without one it stops with "niro startis interactive and there is no terminal to prompt on."Connecting agents needs a browser sign-in.
niro mcp installaccepts only the browser sign-in thatniro startdoes. Afterniro login --api-keyit refuses with "Not signed in. Run niro login".Sending the coverage audit. The audit reads your plan through your
niro loginsign-in before it sends anything, so on a machine with no sign-in nothing is sent. SettingNIRO_AUDIT_API_KEYdoes not change that: the key only replaces the upload's own sign-in header. When the sign-in is missing,niro audit-sendsays so: "Nothing sent: not signed in. The audit reads your plan through yourniro loginsign-in, so runniro loginfirst."
What works
- Confirming without a prompt.
niro uninstall --yesandniro audit-push-repo --yesskip their question. Without a terminal they need--yes, and refuse without it. - Signing in with a key from a pipe.
niro login --api-keyreads 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.