Navig

NAVIG

No Admin Visible In Graveyard

The terminal was never the problem. The chaos around it was.

[!NOTE]

NAVIG 3.x is a stable release. The CLI contract (navig ) is stable

and changes follow semantic versioning. Review the CHANGELOG

before upgrading across major versions. As with any tool that operates live infrastructure, use

read-only inspection and dry runs first in production-critical environments.

---

See it in action

Real sessions, recorded from the tapes in tools/showcase/ against lab hosts — nothing typed into the output, nothing edited out. All eleven scenes, the videos and how they were made: [docs/showcase](docs/showcase/README.md) · videos (and a 90-second trailer) on the NAVIG 3.25.0 release.

Live dashboard — navig dashboard

Hosts & safety — host test , a second session refused, a destructive command declined

Spaces — space init --dry-run → space init → space doctor

Blocks — block show → apply --dry-run with per-step risk

Ledger & undo — ledger show → ledger verify → undo --list

Your node — navig whoami

---

Prerequisites

NAVIG CLI uses Nerd Font glyphs for Powerline-style status bars and icons. Install once per machine:

pwsh navig/builtin/scripts/Install-NerdFont.ps1

VS Code is patched automatically on all platforms. Restart VS Code and your terminal after running the script.

Offline install: set $env:NAVIG_FONT_ZIP to a local zip path, or pass -LocalZip .

---

What is NAVIG?

NAVIG is a terminal-first infrastructure CLI and runtime for people who are tired of juggling SSH sessions, scattered scripts, disconnected dashboards, and ad-hoc credentials just to keep their systems running.

It was built by one person — a solo founder managing a growing swarm of remote machines, projects, and operational overhead with no platform team to fall back on. The problem wasn't the terminal. The problem was everything fragmented around it: SSH in one place, SFTP in another, databases behind dashboards, secrets pasted into notes, logs spread across providers, and no single coherent surface to operate from.

NAVIG is the result of refusing to accept that reality.

It gives operators direct control over remote hosts, databases, containers, files, tunnels, and workflows — from one place, with structure, memory, and optional AI assistance that stays out of the way until it's actually useful.

One operator surface. For operators.

---

NAVIG Core (free) vs NAVIG Deck (paid)

NAVIG ships in two layers with a deliberate split:

• NAVIG Core (this repo) — Apache-2.0 open source. The daemon, CLI, agent runtime, vault, scheduler, mesh, MCP server, Telegram text bot, gateway. Free forever, no host limits via the CLI, no telemetry.
• NAVIG Deck — the polished UI cockpit (proprietary; signed PyPI wheel installed via pip install navig[deck]). Hosts inventory, mesh topology, vault UI, mission queue, workflow runner, Telegram Mini App. Free on one host; Harbor Pass / Max add host scale and the full operator module suite — see navig.run/deck.

The split is honest: the daemon is open and audit-able, the Deck is free on one host, and Harbor subscriptions add host scale, every operator module and all of Harbor Bay. See navig.run/buy for the plans.

What's free, forever, no matter what:

• The entire CLI — unlimited navig ssh, unlimited hosts you connect to
• Telegram text bot (/start, /run, /status, all commands)
• Agent runtime (navig ask, conversation memory, missions)
• VS Code MCP integration
• Vault, scheduler, mesh peer discovery
• All updates, including major versions

What a Harbor subscription pays for is scale and the operator suite; the daemon never will be paid.

---

Why NAVIG?

Most operators already have SSH. What they don't have is everything that should live around it:

NAVIG is not a configuration management tool (not Ansible). It is not a deployment platform (not Kubernetes). It is a control plane for humans — the thing you reach for when you need to do something to a real machine, right now, without writing a playbook.

---

Features

---

Install

Linux / macOS / WSL

curl -fsSL https://navig.run/install.sh | bash

Windows (PowerShell)

iwr -useb https://navig.run/install.ps1 | iex

pipx

pipx install navig

pip

pip install navig

Install options

Telegram bootstrap is available through the installer pipeline after install:

NAVIG_TELEGRAM_BOT_TOKEN="<your-bot-token>" navig init --profile operator

Development Install

git clone https://github.com/navig-run/core.git navig

cd navig pip install -e ".[dev]"

With a virtual environment (optional but recommended):

git clone https://github.com/navig-run/core.git navig

cd navig python -m venv .venv source .venv/bin/activate # Windows: .venv\Scripts\activate pip install -e ".[dev]"

Verify

navig --version

navig --help

---

No server? Start here (local mode)

If you don't have a remote server available yet, NAVIG works on localhost too:

# Install

pip install navig

Discover your local machine as a host

navig host discover-local

Run your first command (on this machine)

navig run "echo hello from NAVIG && uname -a"

Explore files

navig file list ~ --tree --depth 2

Ask the AI operator layer something

navig ask "what process is using the most CPU right now?"

That's a complete first run — no remote server required.

---

Quick start

# 1. Initialize — creates ~/.navig/, runs setup wizard

navig init

2. Add a remote host

navig host add

3. Test the connection

navig host test

4. Set it as active

navig host use

5. Run your first remote command

navig run "uname -a"

6. Ask the AI operator layer something about it

navig ask "what is consuming the most memory on this host?"

That's it. Everything else builds from here.

No server yet? examples/quickdemo.sh walks the same path on your own machine in 60 seconds.

Where to go next — after that first navig run:

| navig tunnel 5432 | Open an