Dedicated tab groups keep parallel work isolated.
Source-available · Electron · MCP
Give your coding agent a browser it can come back to.
Hronaut is a visible desktop browser that keeps tabs, sign-ins, cookies, local storage, IndexedDB, and window state alive between agent sessions.
Free for permitted noncommercial use. Commercial use requires an active paid subscription.
- Local
- MCP endpoint
- Visible
- human handoff
- Durable
- browser profile
Sessions survive restarts and client disconnects.
Why Hronaut
A real browser session, not a disposable automation process.
Keep the convenience of browser automation without losing visibility, state, or the ability to take over.
Persistent by default
Cookies, cache, storage, tabs, bookmarks, and window state remain available when an AI session ends.
Human-visible control
Watch what happens and take over for authentication, consent, payment, CAPTCHA, or visual judgment.
Agent-safe workspaces
Every agent creates its own named tab group instead of touching your Default tabs or another workflow.
Built for debugging
Inspect Console, Network, accessibility, performance, storage, screenshots, responsive layouts, and visual changes.
Local security boundary
The server stays on loopback and uses an owner-only profile token. Sensitive browser state stays on your machine.
One browser, many clients
Connect any compatible coding agent through a standard Streamable HTTP MCP endpoint.
A practical loop
Open once. Reuse the session for every task.
- 1
Launch Hronaut
Your local browser profile and MCP server start together.
- 2
Connect the agent
Copy the endpoint and profile token from Hronaut Home.
- 3
Keep the state
Close the task. The browser, tabs, and authenticated sessions remain.
Commercial licensing
One license per person. Three devices per seat.
For companies, freelancers doing paid work, and anyone using Hronaut to deliver a commercial product or service.
Noncommercial
For personal, educational, hobby, research, and qualifying nonprofit use under PolyForm Noncommercial.
- Full source code available on GitHub
- Build and inspect the application yourself
- No commercial or paid-client use
- Community support through GitHub
Commercial seat
Equivalent to $5/month, billed annually — 50% off $120.
- Commercial use by one named user
- Up to 3 active devices
- Updates while the subscription is active
- Use by employees or independent professionals
- Commercial rights for the active subscription period
Secure Creem checkout is loading.
Clear boundaries
Source-available, with commercial rights sold separately.
Noncommercial use
The public source is licensed under PolyForm Noncommercial 1.0.0. The license text controls what is permitted.
Commercial use
Companies and independent professionals need an active paid subscription before using Hronaut for business or paid client work.
Paid commercial use
An active subscription grants commercial use to the named users and device limit purchased. Redistribution and sublicensing are not included.
The checkout summary is not a substitute for the applicable license agreement. Review the repository license documents before use.
FAQ
Before you install.
Is Hronaut open source?
The source is public and inspectable, but PolyForm Noncommercial is not an OSI-approved open-source license because commercial use requires a separate license. “Source-available” is the accurate description.
Who needs a commercial subscription?
Companies, employees using Hronaut for work, freelancers using it for paid client work, and products or services that benefit commercially from Hronaut.
How do company licenses work?
Buy one named-user seat per person who uses Hronaut. Each seat may be active on up to three devices. Quantity is selected in Creem checkout.
What happens if I cancel?
Commercial rights continue only until the cancellation effective date shown by Creem. An immediate cancellation ends access immediately; a scheduled cancellation continues through the stated date. Open the Creem Customer Portal to manage or cancel a subscription.
Does Hronaut upload browser data?
Hronaut is designed around a local browser profile and loopback MCP endpoint. Review the source and release notes for the exact behavior of your version.
Where can I get help?
Email [email protected] for billing, licensing, cancellation, or refund support. Use GitHub Issues for reproducible product defects. We aim to answer customer support requests within three business days.
Keep the browser. Change the agent.