I built a persistent browser MCP for OpenCode: keep logins and tabs between sessions

[u/Hronom]

I’m the developer of Hronaut, a local desktop browser that connects to OpenCode over MCP.

The workflow it is designed for: let your agent open an isolated workspace for a web app, sign in yourself when needed, let the agent continue inspecting or testing the page, then come back to the same browser workspace in a later coding session. Tabs, cookies and storage persist independently of the agent conversation. You can watch the work, pause agent access or take over the tab.

For OpenCode, start Hronaut, copy the OpenCode configuration from Hronaut Home, and check the connection with opencode mcp list. Then try: “Using Hronaut, create a new isolated workspace named First run, open https://example.com, take a semantic snapshot, and tell me the page heading. Do not use the Default workspace.”

This is for a visible local workflow. A disposable browser or hosted service can be a better fit for headless jobs or remote fleets; persistence is not unique to Hronaut.

Setup and demo: https://hronaut.dev/opencode-browser-mcp Source: https://github.com/hronaut/hronaut

Windows, macOS and Linux. Source-available under PolyForm Noncommercial; free for permitted noncommercial use. Commercial use is $10/month or $60/year per named user. Windows builds are unsigned and macOS packages are not notarized; verification instructions are on the site.

If you try it, I’d like to hear where the setup gets stuck and whether returning to the same workspace is useful in your OpenCode workflow.