HRONAUT
Download

Gemini CLI browser MCP

Give Gemini CLI a browser that stays open.

Hronaut owns a separate visible Chromium browser. Gemini CLI connects over loopback MCP, while tabs, sign-ins, cookies, storage, windows, and named workspaces remain available after one CLI process exits.

Download HronautCopy Gemini CLI setupCompare browser tools

Hronaut is an independent project and is not affiliated with or endorsed by Google.

Local MCP endpoint

http://127.0.0.1:47812/mcp

Start Hronaut once. Gemini CLI can disconnect, restart, or switch repositories without owning the browser process. The endpoint listens on loopback rather than exposing a hosted browser.

Choose the ownership boundary

Gemini CLI already has browser choices. Hronaut serves a different lifecycle.

Gemini CLI's experimental built-in browser agent supports persistent, isolated, and existing session modes. That is a good fit when Gemini should own or attach to the browser for its run. Choose Hronaut when you want a separate visible desktop process with named profiles, explicit human pause and takeover, and one browser that can continue across Gemini CLI, Codex, Claude Code, and other MCP clients. Official Gemini CLI browser-agent modes ↗

Separate process

Exit Gemini CLI, keep the session

The Hronaut desktop application owns Chromium and its profile. A Gemini CLI process can end without intentionally closing Hronaut or discarding its local browser state.

Human control

See, pause, and take over

Watch browser actions, pause MCP before a sensitive step, sign in yourself, then resume Gemini CLI inside the same browser session.

Cross-client continuity

Use one browser with multiple agents

The same named Hronaut workspace remains available when you move between compatible MCP clients. The browser does not belong to one CLI transport.

Local boundary

Browser data stays on this device

Hronaut is a local Electron/Chromium application with a loopback MCP endpoint. It is not a hosted browser, proxy, CAPTCHA service, or multi-browser CI runner.

One user-level command

Connect Gemini CLI to Hronaut.

Gemini CLI supports Streamable HTTP MCP servers and user-scoped configuration in ~/.gemini/settings.json. The user scope makes Hronaut available across repositories on this computer.

Authentication disabled

Run from any repository

gemini mcp add --scope user --transport http hronaut http://127.0.0.1:47812/mcp

The command combines Gemini CLI's documented HTTP transport and user scope. Official Gemini CLI v0.57.0 MCP options ↗

Authentication enabled

Copy from Hronaut Home

Enable Require MCP authentication, then copy the generated Gemini CLI configuration from Hronaut Home. It adds Hronaut to mcpServers with the current endpoint and authorization header. Keep that owner token out of chat, screenshots, shell history, issues, and source control.

Verify before using a login

Prove the connection in an isolated workspace.

  1. 1

    Check the configured server

    Start Hronaut, then run gemini mcp list. Hronaut should show the same Streamable HTTP endpoint displayed on Hronaut Home.

  2. 2

    Check it inside Gemini CLI

    Run /mcp list for detailed status and connection diagnostics before asking Gemini to touch a signed-in page.

  3. 3

    Create a clean first workspace

    Ask: “Create a Hronaut workspace named first-check, open https://example.com inside it, and tell me the page title and workspace ID. Do not use my Default workspace.”

  4. 4

    Confirm the observable result

    A visible first-check workspace opens Example Domain, and Gemini CLI reports its stable workspace ID.

Security boundary

Treat page content and local tool access as untrusted until reviewed.

A new Hronaut profile starts without MCP authentication for simple local setup. In that mode, another process running as your operating-system user could connect. Before using valuable signed-in sessions, enable Require MCP authentication and copy the exact token-aware configuration from Hronaut Home.

Websites can contain prompt injection, and a persistent authenticated browser carries the authority of every site signed in inside that profile. Keep sensitive work isolated, review surprising requests, and use Hronaut's pause and interaction-lock controls before entering passwords, security keys, payment details, or other human-only information.

Choose deliberately

Use Gemini's browser when Gemini should own it. Use Hronaut when you should.

Gemini CLI's built-in browser agent is a valid choice for Gemini-owned browser work. Its own lifecycle code closes browser managers on /clear and CLI exit. Choose Hronaut for a separate visible browser that should outlive one CLI process, preserve named workspaces, support explicit human handoff, and remain available to other MCP clients. Official lifecycle source ↗

Last verified against Gemini CLI v0.57.0 on August 27, 2026.

Choose a desktop packageAll client setupSafe login handoffInspect the source