Test web apps with your coding agent. Local MCP browser with persistent tabs; pause or take over. Source-available. 10-day trial, then $4/mo or $24/yr.
Try Hronaut with one small task:
Create an isolated workspace, open https://t.co/IH9AYShWJu, and ask your coding agent for the page heading. Keep the browser open after the task ends.
A local browser you can return to.
Setup: https://t.co/ndHr11tK11
Checking a local app with Hronaut? Give your coding agent one concrete job: open the settings page, change a disposable preference, reload, and report whether it persisted.
A click isn't the result.
Paid browser; bring your own agent/model.
https://t.co/ndHr11tK11
Hronaut 2.8.8 adds a pre-dispatch license-expiry check and in-app renewal notice for delayed agent actions. It also settles cancelled searches promptly. 10-day free trial, no card/auto-billing; then $4/mo or $24/yr per named user: https://t.co/fUpEAnYfBm
Hronaut v2.5.28: remote MCP off by default; restart to apply. Token auth defaults off; without it, reachable users can control tabs/attach files. HTTP is unencrypted. Enable auth; firewall the listener. 10-day trial; then $4/mo or $24/yr per named user. https://t.co/kR04qfl7SM
Need an agent to use a signed-in web app? Hronaut keeps the browser visible and lets you take over at sign-in or MFA, then hand control back to the agent. See how the handoff works: https://t.co/fUpEAnYfBm
Need an agent to use a signed-in web app? Hronaut keeps the browser visible and lets you take over at sign-in or MFA, then hand control back to the agent. See how the handoff works: https://t.co/AquxGFndFi
Hronaut v2.5.19 adds pause/resume for downloads in the current session—from the Downloads panel or workspace-scoped MCP controls. It also fixes a mock-response header edge case when adding request conditions in the UI or MCP. Release notes: https://t.co/Wtm6N8m7cw
Hronaut v2.5.18: stale recording starts are rejected after newer tab actions; native download listeners release on close/finish; shutdown rejects new wallet requests and late transaction prep, cancelling waiting approvals. Release: https://t.co/enQNlBXqmV
Hronaut v2.5.16 is out. Agents now see the exact fork action for metadata-only workspaces. Also fixed sleeping-tab previews, release-history pagination, and stale panels after same-page navigation. https://t.co/5M14xMUSNE
Your coding agent can finish a run without resetting browser context.
Hronaut keeps named workspaces and tabs in a visible local browser between sessions. Watch, pause, or take over when sign-in/2FA needs you.
10-day trial, no card or auto-billing: https://t.co/mavGipTRQP
@kalapowered Add one case: a timeout after commit. Reconcile authoritative state before retrying; if the observer is unhealthy, mark the trial inconclusive. Otherwise a retry can duplicate the side effect. Hronaut’s rule: final state and prohibited side effects—not screenshots alone.
@AxiomBot@dnzxlyfe Bind preflight to an action intent: verb, origin, policy generation, and operator scope. Store it before dispatch and bind read-back to it. If page/policy changes while approval is pending, emit unknown/reconcile—not a blind retry. Later logs can’t prove authorization.
AgentEye’s post-fix scan moved Hronaut from 74/100 to 78/100; Docs/API Readiness improved 3/15 → 7/15 after we shipped #257: https://t.co/FGArh5RwBb. The scan is a heuristic, not traffic or revenue. https://t.co/Hg3pbqUNSX
AgentEye’s scan of Hronaut: 74/100. It surfaced a Docs/API extraction gap (3/15), so we opened follow-up issue #257: https://t.co/FGArh5RwBb. Transparent feedback beats vanity metrics. https://t.co/Hg3pbqUNSX
Can a coding agent reconnect and find the same browser tab and page state?
We’re looking for 5 users to run a 20-minute Hronaut test on a public page or localhost. Windows/macOS/Linux; 10-day trial, no card.
https://t.co/dJf0QnVCFT
Hronaut team; drafted with AI help.
@P1xeltechco Tried Web design in Chrome: 13h extra, 12h swapped, £60 left. The preview agrees, and 0h/day correctly blocks it. Do you rerun these cases manually after changes? Hronaut maintainer; AI-assisted feedback.
@nitinkrishnak I checked the public page: “Get started” is disabled and sign-ups open at launch. A “Request beta access” CTA would connect this invite to the site. Is there a public sandbox for the human-handoff flow? Hronaut maintainer; AI-assisted.
Real Hronaut 2.4.24 source + local Anvil: reject → submit → pending → confirm the same hash.
Own provider, no real funds. Test harness clicks approval controls—not agent self-approval.
AI-assisted production. Video + limits: https://t.co/CXLAsu9Vo2
Wallet picker loaded after the provider? Test discovery before signing.
Our Hronaut v2.4.22 source/jsdom check: 3 scenarios, 2 broken variants caught, 0 wallet requests.
Repro + limits (not a live-dApp test or audit): https://t.co/wjvGmI9hqF
@kirjd@mehul_kapadia_@HimanshuJasaiw1 Is this web or native app testing? For web flows, browser-scoped input can avoid fighting over the OS cursor. I maintain Hronaut, a separate local MCP browser—not native-app automation. Which agent/OS are you using? AI-assisted.
@ednevsky@Hronom For the “tomorrow” part, save a short handoff in the repo: goal, last verified result, next step. Have the agent read it before resuming the browser workspace. Which agent/client do you use? I maintain Hronaut; AI-assisted.
@coinspect The checksum example in your write-up suggests a useful negative control: deliberately reject in the dApp before dispatch. The reviewer should label wallet behavior "not exercised", not "passed". Then compare with the same input actually reaching the wallet.