When you are new to a codebase, Niro gives you its shape before you read any file. It shows the services, how they call each other, the routes they serve, the data they keep and the events they send.

See it in a browser

niro ui

This opens a page that draws the graph. It runs on your computer only (at the address 127.0.0.1, on port 8601 by default), it is read-only, and it stops when you press Ctrl-C.

Ask in the terminal, or let your agent ask

Question Tool, or command
Which service calls which? get_service_topology
Which routes does this code serve? find_api_endpoints
Which other services does it call? find_outbound_http_calls
Which tables and stores does it use? list_data_resources, then get_data_resource_usage
Which events does it send and handle? list_events, find_orphaned_events
Which classes exist? list_types
Which folders are separate services? niro modules

If services are linked wrongly or not at all, you can tell Niro where they live. See Configure a folder.

Playbook

Learn a new codebase walks the first six questions on Keycloak and on a synthetic monorepo of 68 services.