At a glance
- Category
- Browser agents
- Tags
- Free trial, Self-hosted
For developers
- Works with
- Goose, Grok Build, Qwen Code, Codex, Claude Code, OpenCode and 20 more
What is Hronaut?
Hronaut is a local browser workspace for coding-agent teams that keeps tabs, sign-ins, and task context visible while exposing actions through an MCP tool contract. It includes visible MCP execution, verified read-back, split view, safe login handoff, and durable sessions across prompts. Hronaut integrates with Claude Code, Cursor, VS Code/Copilot, and GitHub. It offers a 10-day trial and a $24/year subscription seat.
What it actually does
Hronaut runs as a standalone desktop application (Windows, macOS, Linux) that exposes a local MCP server over loopback HTTP. Coding-agent clients (Claude Code, Cursor, Codex, VS Code/Copilot, OpenCode, or any Streamable HTTP MCP client) connect to it and drive a real, visible Chromium window instead of a headless or extension-owned tab. The pitch is continuity: sign into a site once in a named workspace, and the tabs, cookies, and storage for that workspace stay available the next time an agent (or a different agent client) connects, rather than resetting per session. Source: vendor homepage and setup docs (hronaut.dev, hronaut.dev/setup).
Where it differs from the alternatives — in the vendor's own words
Hronaut publishes a comparison page against six other browser-MCP approaches (Playwright MCP, agent-browser, Chrome DevTools MCP, Browser MCP, Browser Control, Browserbase) and is unusually candid about not overclaiming: it explicitly corrects itself — "Playwright MCP preserves login state, cookies, and local storage by default. Hronaut should not claim otherwise" — and frames its actual distinction as owning a separate, visible desktop browser with named workspaces and explicit human pause/takeover, independent of any single agent client's lifecycle, rather than being the only tool that persists a login. Source: hronaut.dev/browser-mcp-guide.
Security architecture and release verification
Hronaut binds its MCP listener to 127.0.0.1 only and validates the Origin header against loopback origins (DNS-rebinding guidance from the MCP Streamable HTTP spec); bearer authentication is opt-in and off by default on a new profile. Renderer views for site content are created with contextIsolation, sandboxing, and nodeIntegration disabled, per the vendor's security page, which links directly to the relevant source files (tabs-manager.ts, main/index.ts) rather than just asserting it. Every release asset ships a SHA-256 checksum manifest and a GitHub build-provenance attestation that can be verified with gh attestation verify. None of this has been through an independent third-party security audit as far as this review could establish. Sources: hronaut.dev/security, github.com/hronaut/hronaut/blob/main/.github/SECURITY.md.
Install friction: unsigned binaries
Windows and macOS packages are not code-signed or Apple-notarized, so SmartScreen and Gatekeeper will warn on first launch. The vendor states this directly on both the download and security pages and gives a checksum-plus-attestation verification path as the mitigation, rather than instructing users to just click through the warning. Source: hronaut.dev/download.
How new and how small this actually is
The GitHub organization and repository (hronaut/hronaut) were created on 23 August 2026 — three weeks before this review — and the domain hronaut.dev was registered the same day. As of 11 September 2026 the repo has 2 stars, 1 fork, and 2 watchers. Of 671 total contributions, 586 are from the sole named contributor (Yevhen Tienkaiev, GitHub handle Hronom) and the rest from the repo's own CI bot — there are no other human contributors. All 5 open issues at review time were filed by that same developer as his own roadmap items (e.g., publishing to the official MCP Registry, scoping delegated browser capabilities), not community bug reports. Development pace is fast — the project is already at release v1.26.1 with commits merging same-day — but that reflects one person's output, not community validation. Sources: api.github.com/repos/hronaut/hronaut, api.github.com/repos/hronaut/hronaut/contributors, api.github.com/users/Hronom.
Pricing and licensing
10-day free trial, full functionality, no card required, starting from the first agent tool call. After that: $4/month or $24/year per named user (the annual price is stated as 50% off $48/year of monthly billing), each seat usable on up to 3 devices. Every use case pays — personal, educational, nonprofit, and commercial all require the same paid subscription after trial; there is no free tier for ongoing use. The source code is publicly readable on GitHub, but it ships under the "Hronaut Subscription and Trial License," a proprietary source-available license: it explicitly disallows redistribution, resale, sublicensing, or offering Hronaut as a hosted service without separate written permission, so "source available" here does not mean open source. Refunds: 14 days on a first purchase, 7 days on a renewal charge, no reason required, processed by Creem as merchant of record. Sources: hronaut.dev (pricing section), raw.githubusercontent.com/hronaut/hronaut/main/LICENSE, hronaut.dev/refunds.
The 71-tool MCP surface
Hronaut's own catalog groups 71 named MCP tools into six areas: workspace/tab/storage management (18), navigation and semantic interaction (17), environment and capture — screenshots, PDF, JS eval (7), QA/audit/reproduction tooling — accessibility, performance, memory, console, HAR-adjacent diagnostics (16), network diagnosis including request replay and routing (7), and mediated local crypto-wallet operations for EVM/Solana/Tron that the vendor says never return private keys (6). The vendor is specific that safety annotations (read-only/destructive hints) are advisory only and real enforcement happens via workspace ownership, token auth, and interaction locks — worth noting since MCP tool-hint metadata is often mistaken for an authorization boundary. Source: hronaut.dev/browser-mcp-tools (verified by vendor against source on 2 September 2026).
Hronaut price and terms
Terms
- Free trial
- Yes10 days
For AI agents
- MCP server
- YesChecked by us,
Where these prices come from
hronaut.dev, checked
What we checked on Hronaut
What the price counts
Priced per seat: one named user per seat at $4 per seat/month or $24 per seat/year, with a seat quantity picker at checkout and each seat covering up to three active devices.
1 seat · $4 / month before applicable tax
hronaut.devChecked
MCP server
Its MCP server is in the official MCP Registry
io.github.hronaut/hronaut
registry.modelcontextprotocol.io/v0.1/s…Checked by us,
Open source
Code on GitHub under a proprietary licence
All rights reserved except as expressly granted below.
github.com/hronaut/hronaut/blob/main/LI…Checked by us,
Hronaut alternatives
Hronaut and its 2 alternatives
All 2 show a price.
Hronaut beside its alternatives: the price on each one's site and the day it was checked Tool Price Checked Hronaut From $4 a seat a month TinyFish Free, then $0.002 per minute ERIUS PHONE From about $44 a month
Questions about Hronaut
- How much does Hronaut cost?
- Hronaut costs $4 a seat a month. From hronaut.dev/#pricing, checked 2 November 2026.
- Does Hronaut have an API or an MCP server?
- Hronaut has an API. Hronaut has an MCP server. We checked the Official MCP Registry ourselves on 15 November 2026.
- Is Hronaut open source, and can you host it yourself?
- Hronaut is not open source. We checked github.com/hronaut/hronaut/blob/main/LICENSE ourselves on 15 November 2026. You can host Hronaut yourself.
- What have we checked on Hronaut?
- 3 facts, under these headings: What it costs to start, how you build with it.
- How do we check Hronaut?
- We hold 3 facts on Hronaut, quoted from 3 pages. Facts last checked 15 November 2026. Price last checked 2 November 2026. Last change found 15 November 2026.
Hronaut price history
Plans for Hronaut started at $4 a seat a month on all 3 of our reads, from 25 October 2026 to 17 November 2026.
| Price | Plan | First seen | Last seen | Readings | Source |
|---|---|---|---|---|---|
| $4 a seat a month | Pricing and trial | 25 October 2026 | 17 November 2026 | 3 | Pricing page, read 25 October 2026 |
From our research, read twice since 25 October 2026, and one of our own checks, on 17 November 2026. 3 more of our checks could not pick this price out of the page and are left out. A date is when we read the page, not when the price changed.
Similar to Hronaut
- ClineFlowGit-native project memory and handoffs for coding agents.
- SmitheryPublic MCP server registry, now run by Arcade, listing direct vendor MCP URLs after its proxy shut down.
- UI DiscoveryA library of real websites, iOS apps and dashboards with each one's palette, fonts and original build prompt.
- AgentMailEmail provider where agents send, receive and thread mail, with webhooks and websockets for incoming messages.
From our research
- Best free AI agents: 10 tools with real free tiersTen free AI agents with real free tiers and no trial bait, with current pricing and the limits and use cases that matter.
- Best sales agents for marketing teams, and what to checkApollo suits teams starting free, VoiceDrop suits voicemail campaigns, and PipeLime suits hands-off email and LinkedIn prospecting.
- Which browser automation API should you build an agent on?Skyvern, Browserbase, Browser Use, Playwright MCP, Hyperbrowser, and TinyFish compared on credential handling, session isolation, and audits, not speed.
Is Hronaut yours?
Free, and the page then carries the verified owner mark. You confirm it with an email at hronaut.dev. Claim this listing
Report an error if a fact is wrong.