First time opening Navide. It shows an onboarding wizard with several checks. What do I actually need to have installed beforehand, and what is a sensible first thing to try?
Before you open it, have at least one supported coding CLI installed and logged in through its own auth flow — Claude Code (claude), Codex (codex), Antigravity CLI (agy), Grok CLI (grok) or another supported one. Navide does not replace the CLI’s installation, authentication, subscription or data policy. Optional: Ollama or a local GGUF model, if you want the local analyzer (intent detection and automatic answers).
Node.js, pnpm, Python and uv are only needed for a source install, not for the packaged app.
What the wizard does, in order:
- Checks the required runtimes and flags any blocked foundation dependency.
- Detects available agent CLIs — confirm at least one is available and authenticated.
- Lets you configure a local analyzer (optional).
- Explains the macOS permissions it may ask for — Automation, Files and Folders, or Full Disk Access — depending on how agents and terminals interact with the workspace. Grant only what the workflows you use need, and read the reason macOS shows first.
- Opens a trusted project folder as the workspace.
After onboarding, Settings → CLI Agents lists every detected CLI with its version, install method and last update result, and can run that CLI’s own update and diagnostic commands.
A first task that cannot hurt:
- Open a disposable or version-controlled workspace.
- Spawn one agent manually.
- Give it a read-only task such as “summarize this repository.”
- Confirm that terminal output, session detection and History update.
- Look at Token Stats if the CLI writes compatible usage logs.
Only after that try a pipeline with a small task, and leave YOLO and Full Auto off until you understand what they bypass (there is a separate topic on the automation modes).
Source: docs/en-US/getting-started.md