hronaut/hronaut

Hronaut is a visible, persistent Electron browser that exposes durable agent workspaces through MCP. It keeps the browser open independently of any individual AI session, so people can watch, pause, and take over while agents work in separate local browser profiles.
Website · Setup · Browser MCP decision guide · Downloads · Issues · Detailed reference
Where Hronaut fits in your agent stack
Hronaut is a local, visible MCP execution layer for agents that already have their own orchestration. The caller keeps workflow and orchestration state; Hronaut binds each browser command to a tool contract and a named local workspace with its own profile, account, origin, and tab context. People can watch, pause, approve, or take over, and the caller can require bounded browser evidence before it treats an external action as complete.
| Responsibility | Owner |
| --- | --- |
| Plan the workflow and retain task state | Your SDK, agent framework, or application |
| Define the requested browser operation | MCP tool contract and arguments |
| Execute with a specific browser identity and site context | Hronaut workspace, profile, account, origin, and tab |
| Approve or complete a consequential manual step | The person using visible Hronaut controls |
| Decide whether the workflow may continue | The caller, using verified postcondition read-back |
For example, a code-first agent can retain its own task state, ask Hronaut to submit a reviewed change in one named workspace, wait for human approval when required, and continue only after verified postcondition read-back confirms the external result.
Hronaut is not an agent framework, hosted browser fleet, no-code platform, or universal production-safety guarantee. Use it when the browser should remain local, visible, and deliberately reusable; keep orchestration and final business decisions in the calling system.
See Hronaut in action
Watch the 35-second product overview, then download Hronaut for Windows, macOS, or Linux.
Not sure which browser model fits your workflow? Read the source-backed Browser MCP decision guide, which compares Hronaut with Playwright MCP, Chrome DevTools MCP, and an extension-based Browser MCP without claiming persistence is unique.
Start in three steps
1. Download the latest Hronaut for Windows, macOS, or Linux and start it.
2. On Hronaut Home, choose your coding agent and copy its generated setup, or use the generic setup guide. The in-app setup always reflects the current local endpoint and authentication choice.
3. Ask the connected agent: Using Hronaut, create a new isolated workspace named “Hronaut first run”, open https://example.com, take a semantic snapshot, and tell me the page heading. Use only that task workspace.
A successful run stays visible in Hronaut, creates an isolated workspace, and remains available after that coding-agent conversation ends.
Ready for a real task? Use the copy-ready starter workflows for authenticated handoff, localhost QA, and responsive review without weakening Hronaut's workspace and privacy boundaries.
For recurring work, run the scheduled and triggered browser workflow. Its disposable Docker fixture shows which component owns triggers, browser authority, human takeover, retries, cancellation, and authoritative outcome reconciliation.
Hronaut automates **web pages in its own browser**, not native desktop applications or other application windows. See browser and native testing boundaries to choose the right test surface, and approval boundaries before consequential actions.
Choose a persistent profile or Hronaut workspaces
A dedicated persistent browser profile can be enough for one project and one identity. Playwright MCP supports this through --user-data-dir; persistence does not require Hronaut. Its profile documentation also explains separate profiles for concurrent browser instances.
Choose Hronaut when you want named profiles managed together in a desktop browser, visible pause and takeover, or deliberate workspace resumption across compatible MCP clients. Each new workspace has separate website storage; bookmarks, history, download records, and remembered permissions remain application-wide. See the workspace contract for the exact boundaries. Hronaut adds a desktop application to run and maintain; its terms are in License.
Each live MCP transport can hold a bounded exclusive write lease for the workspace it creates or resumes. A resume remains usable for read-only inspection when another transport already owns writes, but conflicting mutations return a typed BUSY result without dispatch. Pausing agents, rotating authentication, disconnecting, releasing ownership, or lease expiry revokes that transport's write authority; claim it again only after inspecting fresh state. This lease prevents concurrent writers inside one Hronaut process, not coordination across different Hronaut installations.