An exit code is the number a command hands back when it ends. 0 means it worked. Any other number means it did not. Scripts read it to decide what to do next.
| Code |
Meaning |
| 0 |
It worked. Signing in also ends with 0 when your account is on the waiting list, or when a trial request was sent |
| 1 |
It failed. The message above it says why. This is the code for nearly every failure |
| 2 |
niro docs-send, or an engine LLM option, in this release, which has no LLM documentation |
| 130 |
You pressed Ctrl-C at a question |
| 128 plus a signal number |
An engine command was stopped by a signal |
| 129, 130, 143 |
niro audit-push-repo was interrupted (hang-up, Ctrl-C, or stop). It deletes its masked copies before ending |
Common causes of code 1
- Setup:
niro start with no terminal;
- a computer type with no engine;
- Node older than 18;
- a folder that is missing, protected, or your home folder;
- not signed in;
- the engine download failed;
- the graph database cannot open;
- the build failed;
- over the line limit.
- Sign-in:
- an empty key, email or password;
- an invalid key;
- timed out;
- account blocked, access denied, or the code expired.
- Folders:
- not signed in;
- no engine;
- two folders given;
- a protected folder;
- a folder not added yet;
- over the limit;
- the engine refused.
- Status and plan:
- the folder is not indexed;
- the plan could not be read.
- Uninstall:
- no terminal and no
--yes;
- a step failed.
niro upgrade
| Code |
Meaning |
| 1 |
npm failed or was interrupted |
| 2 |
npm said it worked, but there is no niro in npm's global folder |
| 3 |
The new version could not finish the upgrade (handover failed) |
| 4 |
The refresh did not finish: at least one agent was not refreshed |
| 5 |
This is not the global copy of niro (for example a linked working copy). Use --force to upgrade anyway |
The engine
status --check ends with 0 when the folder is indexed, and 1 when it is not.
- A licence refusal ends with 1.