# Hronaut

> Hronaut is a visible, persistent desktop browser for coding agents. It keeps a dedicated Chromium profile, tabs, sign-ins, storage, windows, and named workspaces available between agent sessions through a loopback Streamable HTTP MCP endpoint.

Hronaut is useful when the browser should belong to the person rather than one agent process: a human can see the browser, pause MCP, authenticate manually, and resume work without placing a password in chat. It supports Codex, Claude Code, Gemini CLI, Goose, Grok Build, Qwen Code, Mistral Vibe, Warp, Zed, JetBrains Junie, Cursor, Cline, Zoo Code, Kiro, Kilo Code, VS Code with GitHub Copilot, OpenCode, and generic Streamable HTTP MCP clients.

## Start here

- [Product and real demo](https://hronaut.dev/): Product fit, pricing status, download link, and a 35-second product capture.
- [Choose a desktop package](https://hronaut.dev/download): Direct Windows, macOS, and Linux downloads with architecture guidance and checksum links. Mac requires macOS 13 Ventura or newer.
- [Release history](https://hronaut.dev/releases): Stable Hronaut release notes retrieved from the canonical public GitHub repository.
- [Setup Hronaut](https://hronaut.dev/setup): Tested connection instructions for supported MCP clients.
- [Official Hronaut Agent Skill](https://github.com/hronaut/hronaut/tree/main/skills/hronaut): Source-available instructions for isolated workspaces, semantic browser actions, private human handoff, and local security boundaries.
- [Hronaut Agent Skill directory](https://www.skills.sh/hronaut/hronaut/hronaut): Public skills.sh listing with the canonical install command and directory security-audit surface.
- [Persistent Browser MCP for Codex](https://hronaut.dev/codex-browser-mcp): User-level Streamable HTTP setup, observable connection checks, shared-client behavior, and security boundaries.
- [Persistent Browser MCP for Claude Code](https://hronaut.dev/claude-code-browser-mcp): User-scoped Streamable HTTP setup, observable connection checks, workspace verification, and security boundaries.
- [Persistent Browser MCP for Gemini CLI](https://hronaut.dev/gemini-cli-browser-mcp): User-scoped Streamable HTTP setup, lifecycle-aware browser comparison, observable connection checks, and security boundaries.
- [Persistent Browser MCP for Goose](https://hronaut.dev/goose-browser-mcp): One-click desktop and local YAML Streamable HTTP setup, observable browser verification, protected-profile guidance, and explicit loopback boundaries.
- [Persistent Browser MCP for Zoo Code](https://hronaut.dev/zoo-code-browser-mcp): Global Streamable HTTP setup, environment-backed bearer authentication, observable browser verification, and the local editor boundary.
- [Persistent Browser MCP for Grok Build](https://hronaut.dev/grok-build-browser-mcp): Official CLI installation, user-scoped native HTTP MCP setup, doctor and browser-task verification, environment-backed bearer configuration, default Ask permissions, and explicit hosted-Grok loopback limits.
- [Persistent Browser MCP for Qwen Code](https://hronaut.dev/qwen-code-browser-mcp): Native user-scoped Streamable HTTP setup, MCP discovery checks, environment-backed bearer configuration, conservative trust defaults, and explicit local-versus-remote reachability limits.
- [Persistent Browser MCP for OpenCode](https://hronaut.dev/opencode-browser-mcp): Stable and V2 OpenCode configuration, observable connection checks, browser-ownership tradeoffs, and security boundaries.
- [Persistent Browser MCP for VS Code and GitHub Copilot](https://hronaut.dev/github-copilot-browser-mcp): Honest built-in-browser comparison, user-profile HTTP MCP setup, observable workspace verification, and local-only security boundaries.
- [Persistent Browser MCP for Cursor](https://hronaut.dev/cursor-browser-mcp): One-click and manual local MCP setup, Cursor-native browser comparison, editor and CLI verification, and security boundaries.
- [Persistent Browser MCP for Cline](https://hronaut.dev/cline-browser-mcp): Explicit Streamable HTTP setup, honest task-scoped built-in browser comparison, IDE and CLI verification, and security boundaries.
- [Persistent Browser MCP for Kiro](https://hronaut.dev/kiro-browser-mcp): One-click and manual localhost HTTP setup for Kiro IDE and CLI, explicit cloud-surface boundaries, observable workspace verification, and security guidance.
- [Persistent Browser MCP for Kilo Code](https://hronaut.dev/kilo-code-browser-mcp): Shared local IDE/CLI MCP configuration, disposable built-in-browser comparison, current Cloud Agent limitation, observable workspace verification, and security guidance.
- [Persistent Browser MCP for JetBrains Junie](https://hronaut.dev/jetbrains-junie-browser-mcp): Shared CLI/IDE JSON configuration, local-only loopback scope, documented MCP status semantics, observable workspace verification, and honest token handling.
- [Persistent Browser MCP for Devin Local](https://hronaut.dev/devin-local-browser-mcp): Current Devin Desktop/CLI user-scoped setup, legacy Cascade migration boundary, owner-token file interpolation, and explicit cloud-loopback limits.
- [Persistent Browser MCP for Zed](https://hronaut.dev/zed-browser-mcp): Custom remote MCP setup for Zed Agent and ACP-forwarded external agents, explicit non-OAuth configuration, observable status checks, and local security boundaries.
- [Persistent Browser MCP for Mistral Vibe](https://hronaut.dev/mistral-vibe-browser-mcp): Shared local CLI and VS Code TOML configuration, explicit static authentication, environment-backed bearer setup, observable verification, and cloud-loopback limits.
- [Persistent Browser MCP for Warp](https://hronaut.dev/warp-browser-mcp): Global file and desktop-settings setup for Warp Agent, observable running state and logs, explicit MCP approval controls, and local-versus-cloud loopback boundaries.
- [Persistent Browser MCP for Windsurf Cascade](https://hronaut.dev/windsurf-browser-mcp): Legacy Cascade and JetBrains plugin setup, accurate Devin Local migration guidance, token-file handling, and explicit local-loopback limits.
- [Test Hronaut with MCP Inspector](https://hronaut.dev/mcp-inspector-browser-testing): Independently verify local Streamable HTTP discovery, separate server and client failures, interpret common connection results, and preserve loopback and authentication boundaries.
- [Test localhost web apps with coding agents](https://hronaut.dev/coding-agent-localhost-browser): Keep one visible local-development tab across edits and server restarts, preserve origin-scoped state deliberately, isolate reproduction data, and choose the right diagnostic or CI layer.
- [Safe authenticated-browser handoff](https://hronaut.dev/authenticated-browser-agents): Human login, pause, and resume workflow plus security boundaries.
- [Parallel agent browser workspaces](https://hronaut.dev/parallel-agent-browser-workspaces): Keep concurrent coding-agent tasks in separate persistent profiles with explicit workspace ownership.
- [Browser MCP and agent browser comparison](https://hronaut.dev/browser-mcp-guide): Source-backed comparison of Playwright MCP, agent-browser, Chrome DevTools MCP, Browser MCP, Browser Control, Browser Controller, Hronaut, and hosted cloud sessions.
- [Hronaut Browser MCP tool catalog](https://hronaut.dev/browser-mcp-tools): Complete source-backed inventory of 71 workspace, interaction, QA, network, and wallet tools with their safety boundary.
- [Why browser lifecycle matters for coding agents](https://hronaut.dev/coding-agent-browser-lifecycle): Architecture guide to task lifetime, MCP transport lifetime, persistent browser profiles, process ownership, concurrency, and human takeover.
- [Security and release trust](https://hronaut.dev/security): Auditable local MCP, Electron renderer, workspace, sensitive-data, and release-provenance boundaries with verification commands and explicit limitations.
- [Local Web3 wallets for coding agents](https://hronaut.dev/local-web3-wallets-for-coding-agents): Source-backed EVM, Solana, and Tron onboarding, website and MCP access, local key custody, trusted approval defaults, the exact short-lived EVM-agent mainnet policy exception, and explicit limitations.
- [Public source](https://github.com/hronaut/hronaut): Application code, releases, issues, and build instructions.
- [Detailed technical reference](https://github.com/hronaut/hronaut/blob/main/REFERENCE.md): Tools, architecture, privacy, permissions, storage, testing, and platform behavior.

## Important boundaries

- The MCP server listens on loopback; Hronaut is not a hosted remote-browser service.
- Hronaut uses Electron/Chromium and does not provide Firefox or WebKit coverage.
- Persistent browser state is not unique to Hronaut. Its distinction is a separate visible desktop application, explicit human controls, and workspaces that remain available as MCP clients change.
- Initial release binaries are not platform code-signed or Apple-notarized.
- Hronaut includes a 10-day trial from the first agent tool call. All users need a subscription afterward: $4/month or $24/year per named user (50% off $48), under the Hronaut Subscription and Trial License. No credit card is required for the trial.
- Production commercial checkout is available for monthly and annual named-user subscriptions through Creem.

- [Split view](https://hronaut.dev/split-view): Compare two live pages, drag the divider, and resize with the keyboard. Includes a real 19-second demo and written steps.