Give your coding agent its own browser.
Keep yours.

Narration: Your coding agent can write the feature. But to check it, it needs a browser. Should that be your everyday Chrome, with your email and your bank? Give it its own browser instead: Hronaut. A visible window, with a separate workspace for each project. When it reaches a login, it stops and calls you. You sign in. The agent never sees the password. Then you hand the tab back. Hronaut gives your agent real debugging tools: the page, the console, the network. So it can find what is broken. Run several agents at once. Each works in its own workspace, so they don’t step on each other. And they stay out of your everyday browser, so they don’t distract you or break your work there. One button mutes every tab. Another blocks your stray clicks and keys, while agents keep working. Give your coding agent its own browser. Keep yours.

On screen: Claude Code is asked to check the Orders page of a local example store admin. Hronaut already holds two workspaces from an earlier Claude Code run. Claude Code creates a third workspace, Acme Store, and opens the sign-in page. It asks for a person and waits, and the tab is marked Needs you. A person types a made-up password and code in the same tab and hands the tab back. Claude Code opens the Orders page in that signed-in session, reads the page, the console and the network requests with Hronaut’s tools, and reports that Revenue today reads $NaN. In a second recording, two Claude Code runs work at the same time, each in its own workspace: one checks a local docs site, the other a local landing page. Home lists both as working and shows what each is doing. While they work, a person presses Mute all tabs and then Block input in the tab rail, and both keep working.

Recorded on November 10, 2026 from an unmodified Hronaut source build with real Claude Code CLI runs. The terminal text is drawn from the run’s prompt and output, the two drawings of browser windows are illustrations, and the sign-in is sped up. No page plays sound in the recording, so the mute button is shown without an audible change. The person’s input is driven by the capture harness. The store admin, the docs site and the landing page are local pages; the account is made up. Not shown: the installer or an external website. The narration is a synthesized voice over original music; sound is optional. Download the video.

Or Watch the recorded reconnect check: a client disconnects, the page stays, and a new client explicitly resumes the workspace. Recorded with Hronaut, MCP test clients, and a local example page. See the exact scope.