Niro CLI
Niro builds a map of your code on your own computer. The map is called the code graph. It records which method calls which, which web addresses (routes) your services answer, which other services they call, and which tables and message topics they read and write. Coding agents ask the graph instead of searching through files, and you can ask it from the terminal.
This documentation ships inside the @niroai/niro package, so it is on your computer even when you are offline.
Start here
cd your-project
npx @niroai/niro@latest start
niro start runs five steps:
- It checks this computer.
- It signs you in.
- It installs the local engine (the program that builds and answers from the graph).
- It builds the graph for the folder you are in.
- It connects your coding agents.
If a step stops, run niro start again: it carries on from the first step that did not finish.
Find what you need
| You want to | Read |
|---|---|
| See where Niro helps in how you build software | How Niro fits your workflow |
| Debug, change, review or test code, step by step | the playbooks, listed in How Niro fits your workflow |
| See how Niro's savings are measured, and check them yourself | Tokens, speed and accuracy, Check what Niro did |
| Connect a coding agent, or use Niro from the terminal | Ways to connect |
| Fix an error message | Troubleshooting, then Error messages |
| Know what leaves your computer | What leaves your machine |
| Check whether your language or framework is supported | Supported languages |
| Look up a command, a tool, a setting or a limit | CLI commands, MCP tools reference, Environment variables, Limits |
| Understand plans and the line limit | Licence and plans |
| Remove Niro | Uninstall |
| Get pull request review or root cause analysis | Features of hosted Niro |