NavGator
Map the dependencies and runtime services a code change can affect before editing them.
NavGator maps the connections behind a change
A table, API route, queue, or service rarely changes alone. NavGator scans a project and builds a graph of components and their relationships. A developer can ask what a proposed change may affect, follow a data path, or connect a failing runtime service to the code that supplies it.
Static scans make the map inspectable
NavGator discovers packages and infrastructure, parses supported source languages, and records known connection patterns such as API calls, database access, and queue consumers. Swift and Rust navigation adds type and module relationships. File hashes tell the scanner what changed since the last pass. The graph comes from source analysis and explicit rules rather than a model’s interpretation of the project.
Impact analysis leads to the affected components
An impact query starts with one component and walks its connected readers, writers, and services. The result identifies files and runtime identities that deserve review. A visual graph helps a person inspect the path, while the CLI gives an agent structured results it can use during a code change.
Fresh CLI calls read current project state
Claude Code and Codex use the same navgator CLI as the default agent interface. Each invocation starts fresh and returns an exit code, so a failed scan or missing component has an explicit result. The dashboard exposes a local read surface for a separate process. An MCP server remains available by opt-in for clients that cannot spawn a command; it is not registered by default.
This choice favors current file state over a long-lived server’s cached view. It also keeps architecture tools out of a coding session until the agent calls them.
Model-call mapping stays separate from model use
NavGator can identify provider SDK calls and group similar model use cases in the scanned project. NavGator itself does not call a model to build its graph. It can therefore inspect code even when a project does not build or provider credentials are unavailable.
Install NavGator before scanning a project
Install the NavGator package, then scan a project with navgator scan and inspect a component with navgator impact <component>. The installation guide covers Claude Code and Codex integration.