# Set up Niro

Niro Local builds the graph of your code on your machine and keeps it there, in `~/.niro-local/graph.db`. Your assistant reads it over MCP. Setup is one command, run once per machine, inside your first repo.

## Install and start

Requires Node.js 18 or newer.

```
cd ~/code/my-service
npx @niroai/niro@latest start
```

`niro start` does the first-time setup, in order:

- Checks this machine.

- Signs you in. One browser screen: choose a plan and approve this terminal.

- Installs the local engine.

- Builds this folder's graph.

- Connects your AI assistants.

- Starts a background watcher that keeps the graph current as files change.

Restart your assistant once it finishes. Skills load at startup.

## Add your other repos

Run `niro init` inside each one:

```
cd ~/code/another-service
niro init
```

It adds the folder and builds its graph. To rebuild a folder you already added, run `niro build` in it. `niro build` refuses a folder that is not added yet and points you to `niro init`.

Niro does not index your home folder or the root of the disk. A git repository inside the folder you index is its own project: run `niro init` inside it.

## Check a folder

```
niro status
```

Shows whether this folder is indexed, its last build, your plan, the connected assistants, and whether auto-sync is running. `niro plan` lists every indexed folder and the lines each one uses. See [Plans and the line limit](https://help.niroai.dev/cli/plans/).

## Connect another assistant

`niro start` already connected the assistants it found. To add another:

```
niro mcp install
```

It asks which assistant, writes Niro into its settings, and installs the skills. Restart the assistant afterwards. See [Connect your assistant](https://help.niroai.dev/get-started/connect/) for the command for each of the 14 supported clients.

## Folders set up with Niro web

This version does not upload folders. If you set folders up with Niro web before, `niro start` lists them, says they are no longer uploaded, and offers to index them on this machine. To set one up later, run `niro init` inside it.

## Ask your assistant

Talk to your assistant as usual. It picks the Niro tools by itself. Questions that work well:

- “What breaks if I change PaymentService.refund?”

- “Which services call the /orders endpoint?”

- “Trace the path from POST /api/orders to the database”

- “Where is the order-created event handled?”

- “Find code I can reuse before I write this feature”

## Next

See every command in the [command reference](https://help.niroai.dev/cli/reference-cli/).