Skip to main content
This quickstart adds Navi to a repository you already work in and uses it to answer one real question about that codebase.
You need macOS or Linux, Node.js 22.13 or newer, ripgrep, and an API key for one model provider. Git is needed for flows that inspect revisions or diffs.
1

Install Navi in the repository

The scoped package provides both navi and navi-cli. These docs use npx --no-install navi-cli so each command runs the version installed in this project.
2

Choose a model

Start with Navi’s default tested route:
You can put the same values in the project’s .env file. Prefer another lab? Choose a provider →
3

Ask a repository question

Ask something whose answer should already exist in the code:
A successful first run has three observable parts:
  • Navi reports that it scanned the repository.
  • The answer includes at least one real path/to/file:line citation.
  • The final grounding line says the answer stands, or gives the exact deeper command needed before you rely on it.
4

Let your coding agent call Navi

Navi links its launcher and interop skill under .agents/; it does not copy either one. Compatible coding agents can now discover when and how to ask Navi for a check.
Navi is installed, the repository answer was grounded, and the project-local launcher works.
Next, choose between Ask, Decide, and Check, or see exactly what the agent connection writes.