Onboarding
A new repo with hundreds of thousands of lines, folder names that promise layers the code doesn't have, a file too long for anyone to have fully read, a subsystem with no obvious front door — onboarding is just guessing until something hands you the handful of classes that actually hold the system up.
Ask it. Watch the call.
Give the agent a ticket, the way you already do. It resolves the names on its own, and that is where it guesses. Switch Niro off and it works from the open files. Switch Niro on and you watch it call Niro, read the result, and answer from that.
Now ask it about your code
Paste this into the assistant you connected to Niro:
I'm new to this repo. What are the ten things holding it up?