FAQ: updates
How do I upgrade?
Run niro upgrade. It does three things:
- It installs the newest
nirowith npm. - It refreshes every agent you connected, the engine and the background watcher.
- It tells you to restart your agents.
Your graphs, sign-in and settings stay.
"npm could not replace the package. The usual cause is that your npm global folder needs root"
npm could not write to its global folder. Run the upgrade with the permissions npm needs. Or point npm's global folder at a folder you own. (Exit code 1.)
"Not upgrading: niro is npm-linked to a working copy" or "you are not running the globally installed niro"
The niro you ran is not the copy npm installed for everyone. Upgrade anyway with niro upgrade --force. (Exit code 5.)
"npm reported success, but there is no niro in your npm global folder."
npm finished, but the niro command is not where it should be. Run npm install -g @niroai/niro yourself. (Exit code 2.)
"The version just installed does not support niro upgrade --finish"
The new version could not finish the job. The message lists the commands to run by hand: niro mcp install and niro service install. (Exit code 3.)
"N of M refreshed, K failed."
Some agents were not refreshed. Run niro mcp install --client <id> for each one named, to see why. (Exit code 4.)
"The local engine was not upgraded: <message>. Try again with niro engine install."
niro was upgraded, but the engine was not. Run niro engine install.
Does the engine update by itself?
No. niro upgrade updates it. Niro keeps an engine newer than the published one rather than going back. It does not replace an engine that is running: close your agents and the watcher first.
After an upgrade, answers say to rebuild.
A new major version stores the graph in a new format. Run niro build once.
Two versions of Niro keep rebuilding each other's graph.
Known problem when two versions share one ~/.niro-local. Keep one version on the computer. niro engine status warns when a second engine is on your PATH.
"Heads up: you are not signed in, so each client's installer will stop without refreshing it."
The upgrade itself worked, but your agents were not refreshed: each one's installer stops with "Not signed in", and the run ends "N of M refreshed, K failed". Run niro login, then niro upgrade --finish.
"Folders from Niro web: N folder(s) were set up with Niro web on this machine."
These folders were set up with hosted Niro by an older version. This version indexes on your computer, and no longer uploads them. To keep using Niro in one of them, run niro init in it. niro start offers to do this, up to your line limit.
Do I need Docker? I have an old niro-local-memgraph container.
No. Niro no longer uses Docker or Memgraph. Remove the old container with docker rm -f niro-local-memgraph, and its data with docker volume rm niro-local-memgraph-data.