Blast Radius
Every "small" edit — a renamed method, an added parameter, a bumped enum, a tweaked event payload, a five-line helper — has callers nobody remembered: five call sites, a downstream service, a base class's subclasses, an event's subscribers.
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:
What breaks if I change this? Show me the full blast radius.
Tools behind it
get_blast_radiusEverything a change can reach: the callers that break and the callees that get different input, across services and events.get_impact_analysisWhat breaks if you change a method, class, route or event, with callers across service boundaries.get_reverse_call_chainWho calls this method or class, walking upward.