navigera

navigera is extremely fast browser automation for AI agents, driven from the shell, one command per step. It is a single native binary (Rust, no Node) that speaks the Chrome DevTools Protocol directly:

• Pages come back as a compact accessibility tree with [ref=N] handles.
• Actions use real mouse and keyboard events.
• A named session keeps a warm browser alive between shell calls.
• New tabs, iframes, shadow DOM and alert/confirm dialogs work the same way.

Faster software for a better planet — less energy, less compute, more time for life.

Start

• Install: Every way to install navigera, the platforms it runs on, and which browser it uses.
• Quick start: One session and four commands, from install to a page read.
• A first session: A tour of one session: the page tree and its refs, the commands, naming an element, what comes back.

Guides

• Hand the agent your browser: Give an agent your own signed-in browser, a copy of its profile, or a saved state.
• Drive a browser from a program: One browser on a pipe with navigera serve: one JSON command per line in, one reply out.
• Use a page’s own tools (WebMCP): Call the tools a page registers for agents through WebMCP, and see which ones it offers.
• Switch from agent-browser: agent-browser’s commands and flags, each with its navigera equivalent.

Concepts

• How navigera works: The three ways to run navigera; what it does between commands: waits, settling, tabs, dialogs.
• Supported browsers: Which browsers and engines navigera drives, CI coverage, and how one is found or installed.
• Lightpanda and your own browser: The Lightpanda engine; your own browser, --attach and --profile.
• Electron and natural mode: Electron apps, --electron; --natural: a headless run a page cannot tell.

Reference

• Commands: The navigera command line: sessions, flags and output, with the command list by topic.
• Commands: sessions, tabs and the browser: start, batch, sessions, reset, tabs, status, history, profiles, installers.
• Commands: read the page: goto, the ax tree, text, get, is, eval, find, console, errors, network, locate.
• Commands: act on the page: click, fill, type and the other actions, wait, downloads, screenshot, pdf, screencast.
• Commands: state, emulation and audit: cookies, storage, set, route, clock, init-script, WebMCP, passkey, a11y, vitals and totp.
• navigera –help: The command list exactly as this build prints it.

Agents

• For AI agents: What an agent gets: the skill, the MCP server, and these docs as markdown.
• Skill: The guide navigera install-skill gives an agent, as this version prints it.
• Skill references: The detail the skill sends an agent to: acting on a page and reading one.
• Skill references: inspecting and sessions: Inspecting page and browser, state and emulation, and sessions.
• Skill references: setup and errors: Electron, setup, when something fails.
• MCP server: Run navigera as a Model Context Protocol server for IDE agents, with the setup for each client.

Benchmarks

• Results: Every driver and agent tool on the same scripted session, from one CI run, with how each number is taken.
• Matched operations: One call per op, warm session, median of 10: navigera against agent-browser, playwright-cli, Playwright MCP, Chrome DevTools MCP and browser-use, each in its default output.
• Where navigera is not ahead: Each measure on which another tool beat navigera in the same run.
• Agent eval: A generic coding agent, given only the tool and its docs, finishing real tasks: navigera, Playwright, agent-browser.

Project

• Changelog: What changed in each release, and what is on the way.
• Contributing: How to build, test, benchmark and release navigera.
• Source layout: Where each part of navigera lives in the repository.
• Security: What navigera protects and how, its known exposures, and how to report a problem.

Built from commit 76f8bb2, 7 commits after v0.13.0, of 2026-11-13; navigera --version says navigera 0.13.1. These docs are ahead of the 0.13.0 release: what the changelog lists under Unreleased is not in 0.13.0 yet.