CodeNavi — Connected Setup (hybrid)

The hybrid scenario: your machine is online for the install and for small update downloads, while indexing, search, chat and your code stay entirely on the box — exactly as in the air-gapped install. Same product, same server, same signature verification; only delivery differs.

AI agent installing this for someone? Follow https://codenavi.com/docs/setup-agent.md instead. It is written for agents to execute, step by step.

No internet on the install machine? Use the air-gapped setup — a carried package installs and verifies fully offline.

1. Run the install command from your trial email

# Linux — from your home directory (not inside an existing install)
cd ~ && curl -fsSL https://codenavi.com/trial/install/<your-token> | sh

On Windows 11 (Docker Desktop), in PowerShell — no admin needed:

curl.exe -fsSL "https://codenavi.com/trial/install/<your-token>?os=windows" -o codenavi-install.ps1
powershell -ExecutionPolicy Bypass -File .\codenavi-install.ps1

One command does the whole install:

• Detects your GPU first, downloads second — you get the image built for your card, and a mistaken vendor choice on the trial form doesn't cost a multi-GB wrong download. The opening banner names the release, the GPU build, and how much there is to download.
• Resumable — a dropped connection continues where it stopped instead of restarting the download.
• Verified before it runs — the download is checked against the pinned checksums and the image signature, by the same setup.sh gate the air-gapped install uses.
• Your license key is fetched automatically with your token — nothing to copy out of the email.
• Asks for your codebase (absolute path and a display name), then configures and starts the server, ending with the address to open.

Under the hood the bootstrap downloads the package and then runs the same installer the air-gapped path uses — everything from that point on is identical.

2. Verify

curl -s http://localhost:8765/health | python3 -m json.tool

"status": "ok" means the server is up. From here the two setups are the same product — follow the air-gapped guide from step 3 for the authenticated health check, connecting Claude Code and other MCP clients, and the first searches. Easiest connect of all: the running server's wizard at http://localhost:8765/connect.

3. Updates — the part air-gapped installs don't get

The connected install writes an update channel (.update.conf) with your token. That gives you:

• One-command updates. ./update.sh (Windows: .\update.ps1) checks, downloads only the changed layers, and asks before applying. A typical code-only update is ~25 MB and takes seconds; your .env, license, settings and index are never touched. ./update.sh --check reports without applying.
• A daily update check. It sends exactly two things — your version number and your trial token — never code. Turn it off any time: rm .update.conf in your install folder.
• Installer refreshes. update.sh replaces the server image only. To pick up changes to the install scripts themselves, re-run the one-liner from the folder above your install — it reuses the image you already have and keeps your .env, license and index.

Details, sizes and rollback: Updating CodeNavi.

Differences at a glance

	Air-gapped setup	Connected setup (hybrid)
Getting the package	Signed tarball you download elsewhere and carry over	Downloaded by the one-liner (GPU-matched, resumable)
Install command	tar xzf … && ./setup.sh --airgap	curl -fsSL https://codenavi.com/trial/install/<your-token> \| sh
License key	Ships in the package (or the emailed license.key file)	Fetched automatically with your token
Signature verification	Same gate, fully offline — key and verifier are in the package	Same gate
Updates	Delta packages we send you, applied by hand	./update.sh — ~25 MB typical, plus an optional daily check
What leaves your machine	Nothing	Version number + trial token during install and update checks — never code
Everything else	Identical: local indexing, local search, local-first LLM, same web UI and MCP tools	Identical

What's next

Same as the air-gapped guide: the web UI at http://localhost:8765/ui, connecting your agent, multi-codebase via CODEBASE_CONFIG, and the full setup guide.