Install
Every way to install navigera, the platforms it runs on, and which browser it uses.
curl -fsSL https://raw.githubusercontent.com/andrey-usa/navigera/master/install.sh | sh
Windows (PowerShell):
irm https://raw.githubusercontent.com/andrey-usa/navigera/master/install.ps1 | iex
Or with a package manager: each one installs the same prebuilt binary:
| Channel | Command |
|---|---|
| npm | npm install -g navigera (or npx navigera …) |
| pip / uv | pip install navigera · uv tool install navigera |
| Cargo | cargo install --locked navigera |
| Homebrew | brew install andrey-usa/tap/navigera |
| Scoop | scoop bucket add andrey-usa https://github.com/andrey-usa/scoop-bucket then scoop install navigera |
Then give your agent the usage guide:
navigera install-skill # -> ./.agents/skills (Gemini CLI, Codex, Cline, Kilo, …)
# --claude -> ./.claude/skills, --continue -> ./.continue/skills
Platforms
Linux, macOS and Windows are supported. On Windows, the session socket is a loopback TCP port; clients must present a random token from the session file in your temp directory. CDP runs over a DevTools WebSocket, and Chrome sits in a kill-on-close job object, so Chrome exits when navigera does.
Which browser navigera uses
navigera finds Chrome or Chromium on its own: a system install,
$CHROME_BIN, or a Playwright/Puppeteer browser cache. It uses a system
Chrome first; with none installed it picks chrome-headless-shell (or
Chromium) from a Playwright or Puppeteer cache. Set $CHROME_BIN to choose
explicitly.
For the fastest cold start, use chrome-headless-shell, the same Chrome without its browser UI layer:
navigera install-browser chrome-headless-shell # from Google's Chrome for Testing, used from then on
What it saves, measured in CI, is the chrome-headless-shell line of the benchmarks.
Made from README.md, docs/install.md.