Skip to content
HRONAUT
Product
Use cases

What you can do with Hronaut.

  • Test your local appLet your agent check localhost in a stable, visible browser.
  • Signed-in appsSign in yourself, then hand the session back to your agent.
  • Parallel agentsGive every task its own isolated browser workspace.
  • Resume after disconnectPick up the same tabs when an agent reconnects.
  • Local Web3 walletsApprove wallet requests without exposing keys.
  • Split viewCompare two live pages side by side.
All use cases →
Agents

Connect the coding agent you already use.

  • Codex
  • Claude Code
  • Cursor
  • VS Code / Copilot
  • Gemini CLI
  • OpenCode
All supported agents →
Resources

Reference, security and troubleshooting.

  • Compare browser toolsChoose the right browser ownership model.
  • MCP tool catalogEvery browser tool, grouped by task.
  • Security & release trustWhat is isolated, and how to verify a release.
  • Browser lifecycleHow tasks, connections and the browser outlive each other.
  • Connection troubleshootingWSL, containers, VMs and remote sessions.
  • Release notesWhat changed in every stable release.
All guides →
PricingBlog
Download
Product

Use cases

Test your local appSigned-in appsParallel agentsResume after disconnectLocal Web3 walletsSplit viewAll use cases →

Agents

CodexClaude CodeCursorVS Code / CopilotGemini CLIOpenCodeAll supported agents →

Resources

Compare browser toolsMCP tool catalogSecurity & release trustBrowser lifecycleConnection troubleshootingRelease notesAll guides →
PricingBlogAll guidesGitHub

Facts

Hronaut in short.

What Hronaut is, what it costs, and when another tool fits better. Each answer links the page with the details.

Reviewed: October 28, 2026

Key facts

What it is
Hronaut is a visible desktop browser for coding agents, with a separate workspace for each project. Your agent drives it over MCP, and your everyday Chrome stays out of it. Overview
How agents connect
Over Streamable HTTP MCP, by default at http://127.0.0.1:47812/mcp. The endpoint listens on loopback; other computers need an explicit opt-in. New profiles require the MCP token. Setup
Workspaces
Each named workspace has its own cookies and site storage, and keeps its tabs between agent sessions. Reopening one needs its private resume key; a workspace ID alone grants no access. Parallel workspaces
Human control
You see every action, can pause the agent, sign in or pass 2FA yourself, then hand the tab back. Hronaut does not bypass login or 2FA, and website sessions can expire. Signed-in apps
Platforms
Windows 10 or newer (x64), macOS 13 Ventura or newer (Apple Silicon and Intel), and Linux on x64 and ARM64 (AppImage, DEB, RPM). Download
Browser engine
Electron and Chromium only. There is no Firefox or WebKit coverage. Comparison
Price
A 10-day trial starts with your first agent tool call; it needs no card and never charges you. Then $4/month or $24/year per named user, on up to three devices. Subscriptions renew automatically until you cancel. Pricing
License
The app is source-available under the Hronaut Subscription and Trial License: you can read and build all of it. The Claude Code and Codex plugins and the VS Code extension are open source under the MIT License. What is free
Your data
Browser profiles stay on your computer. Websites receive normal browser traffic, and your agent can receive page contents; if it uses a cloud model, that provider’s data handling applies. Security
Releases
Every package has a SHA-256 checksum and a GitHub build attestation. Windows and macOS packages are not yet platform code-signed or Apple-notarized. Verify a release

When Hronaut fits

  • Test your local app: Let your agent check localhost in a stable, visible browser.
  • Signed-in apps: Sign in yourself, then hand the session back to your agent.
  • Parallel agents: Give every task its own isolated browser workspace.
  • Resume after disconnect: Pick up the same tabs when an agent reconnects.
  • Local Web3 wallets: Approve wallet requests without exposing keys.
  • Split view: Compare two live pages side by side.

When another tool fits better

  • Clean, repeatable tests in CI: use a browser owned by your test runner, such as Playwright.
  • Inspecting the exact Chrome tab where you already reproduced a bug: use Chrome DevTools MCP or Browser MCP.
  • Firefox or WebKit coverage.
  • A cloud browser, proxies, CAPTCHA solving, or unattended remote runs: use a hosted browser service.

Other tools can keep sessions too. Read the full comparison.

How it compares

QuestionPlaywright MCPChrome DevTools MCP · Browser MCPHronaut
Whose browserA managed automation browserYour everyday ChromeA separate desktop app
Where sign-ins liveA project profileYour live Chrome profileA named workspace per project
Best forRepeatable automation and testsDebugging in the Chrome you have openRecurring signed-in checks across projects

Questions

Is Hronaut free?

Every feature is free for 10 days, with no card and no charge when the trial ends. Ongoing use of the app needs a subscription. The plugins and the VS Code extension are MIT-licensed and free. What you can do without paying

Does Hronaut include an AI model or agent?

No. Bring the coding agent you already use, such as Codex, Claude Code, or Cursor. Agent and model costs are separate. Choose your agent

Which agents work with Hronaut?

Any MCP client that supports Streamable HTTP. The site has tested setup guides for Codex, Claude Code, Cursor, VS Code with GitHub Copilot, Gemini CLI, OpenCode, Cline, Goose, Zed, Warp, and more. All supported agents

Is Hronaut a hosted or cloud browser?

No. It is a desktop app on your computer, and its MCP endpoint listens on loopback. An agent running in the cloud cannot reach it directly. Client topology

Does it use my everyday Chrome?

No. Hronaut is a separate app with its own profiles. Agents can use what you sign into in Hronaut, not your everyday Chrome. What an agent can reach

Do I have to give the agent my password?

No. Pause the agent, sign in yourself, and resume, so the password never goes into chat. Once the session is signed in, a connected agent is trusted with it. Signed-in handoff

How is it different from Playwright MCP?

Playwright MCP runs a managed automation browser and suits repeatable automation and tests. Hronaut is a separate desktop app with a named workspace per project, for recurring signed-in checks a person can watch and take over. Full comparison

Where can I follow changes?

Release notes for every stable release are on the releases page and in an Atom feed. The blog has an RSS feed. Release notes

HRONAUT

A visible desktop browser for coding agents, with a separate workspace for each project.

Local-first · Source-available

Follow Hronaut

XBlueskyYouTubeLinkedInGitHubProduct Hunt

Follow the maintainer · Hronom

XBlueskyThreadsDEVRedditHacker NewsGitHub

Product

OverviewProduct tourPricingDownloadRelease notesBlogSource code

Use cases

Test your local appSigned-in appsParallel agentsResume after disconnectLocal Web3 walletsSplit view

Agents

Set up HronautCodexClaude CodeCursorVS Code / CopilotGemini CLIOpenCodeAll supported agents

Resources

Compare browser toolsMCP tool catalogSecurity & release trustBrowser lifecycleConnection troubleshootingRelease notesFacts and questionsAll guides

Support & legal

[email protected]Manage subscriptionGitHub IssuesPrivacyTermsRefunds

© 2026 Hronaut.

Source available under the Hronaut Subscription and Trial License.