Your personal Chrome stays private.
The agent never sees your email, bank or admin sessions.
See what is isolatedA separate browser for your coding agent
One browser per project.
Never your own Chrome.
A separate, visible browser for every project your coding agent touches. Pause or take over any time.
- Windows · macOS · Linux
- Profiles stay local
- Source on GitHub
- Verifiable releases
- 01Install Hronaut next to your agent.
- 02Connect your agent.
- 03Check your app.
Optional: add the Hronaut agent skill
The skill guides isolated workspaces, semantic browser actions, and private human handoff. It does not install Hronaut, configure MCP, or contain secrets.
npx skills add hronaut/hronaut --skill hronautProduct tour · 38 secondsWatch the 38-second product tour
▶
Transcript and capture details
An agent connects to Hronaut over local MCP, creates an isolated workspace called Checkout QA and opens a local example cart. It reads the page, adds one notebook so the total becomes $36.00, and opens the review step. It then asks for a person, and the tab is marked for attention. A person types a review note and confirms the review in the same tab; the page says no payment was sent.
Hronaut Home shows one active MCP session. The first agent disconnects and the count drops to zero, while the workspace, tab and result remain. A second agent connects, finds no workspaces of its own, resumes Checkout QA with the workspace’s private resume key, and reads the saved result.
Recorded at normal speed from an unmodified Hronaut 3.3.1 source build. The demo agents are MCP SDK clients, not a named AI client; the person’s input is driven by the capture harness. Example Store is a local page with example data. Not shown: the installer, a real login or external website, a payment, or an app restart. Original synthwave score. Download the 38-second tour.
Or Watch the recorded reconnect check: a client disconnects, the page stays, and a new client explicitly resumes the workspace.
Already using a free browser tool?
| Question | Playwright MCP | Chrome DevTools MCP · Browser MCP | Hronaut |
|---|---|---|---|
| Whose browser | A managed automation browser | Your everyday Chrome | A separate desktop app |
| Where sign-ins live | A project profile | Your live Chrome profile | A named workspace per project |
| Best for | Repeatable automation and tests | Debugging in the Chrome you have open | Recurring signed-in checks across projects |
Other tools can keep sessions too. Free tools are the right choice for CI or a quick debug. Read the full comparison →
- Local by default
Other computers need your explicit opt-in.
- Sandboxed websites
Every site runs in Chromium’s sandbox.
- Pause any time
Watch every step and take over when you want.
- Verifiable releases
Checksums and GitHub build attestations for every package.
A connected agent is trusted with the visible browser session. See exactly what is isolated and what is not →
Latest releaseWindows, macOS, and Linux packages with SHA-256 hashes and GitHub build attestations.Pricing and trial
Try it on your next project.
All features. One named user. Up to three devices.
10-day trial
$0for 10 days
10 consecutive days from your first agent tool call. No credit card required.
- All browser features included
- No automatic billing after the trial
Subscription seat
$24per seat / year
Equivalent to $2/month, billed annually — 50% off $48.
- Personal and commercial use by one named user
- Up to 3 active devices
- All features and updates while subscribed
- Your AI agent or model is provided separately
1 seat · $24 / year before applicable tax
Secure Creem checkout is loading.
Source-available under the Hronaut Subscription and Trial License. All ongoing use requires a subscription after the trial. Cancellation and refunds · Manage subscription
Cancellation and trial expiry
An immediate cancellation ends access immediately; end-of-period cancellation keeps access through the paid date. Cancellation does not request a refund. After expiry, agent automation stops; browser data remains accessible manually for recovery, export, and deletion. Read the refund policy.
Before you install
A few useful answers.
Does Hronaut include an AI agent?
Bring your own coding agent, such as Codex, Claude Code, or Cursor. Your agent or model costs are separate. Choose your agent.
Can I use it for localhost and signed-in apps?
Yes. Open your local app or sign in inside a project workspace. Website sessions can expire; Hronaut does not bypass login or 2FA. Keep Hronaut and the agent connection running for automation.
What happens after the trial?
The 10-day trial starts with your first agent tool call. No card or automatic billing. All ongoing use requires a subscription. After expiry, automation stops and browser data remains accessible manually for recovery, export, and deletion.
Where does my browser data go?
Profiles stay on your computer. Websites receive normal browser traffic, and your agent can receive page contents. If that agent uses a cloud model, its data handling applies. Read the security boundary.
Why might installation show a warning?
Initial packages are not platform code-signed or Apple-notarized. Verify published hashes and GitHub attestations before installing. Verification steps · Get help.
Give your agent its own browser.
10-day trial from your first agent tool call. No credit card required.