Built-in browser
One Cline task
Use Cline's browser action when the browser is temporary task machinery and cleanup at completion is desirable.
Cline browser MCP
Hronaut runs a separate visible Chromium application. Cline's IDE extension or CLI connects over loopback MCP while named browser workspaces remain available after a Cline task ends or when another compatible local MCP client takes over.
Hronaut is an independent project and is not affiliated with or endorsed by Cline.
Local MCP endpoint
http://127.0.0.1:47812/mcpHronaut listens on loopback. It works with Cline clients running on the same machine and is not a hosted browser for remote agents.
Use Cline's built-in option when it fits
Cline's browser_action tool uses Puppeteer for navigation, coordinate clicks, typing, screenshots, and console capture. Its documented task lifecycle includes Automatic cleanup on task completion. For a browser that belongs to one Cline task, use the built-in tool. Official Cline browser lifecycle source ↗
Built-in browser
Use Cline's browser action when the browser is temporary task machinery and cleanup at completion is desirable.
Cline MCP
Cline supports local stdio servers plus remote Streamable HTTP and legacy SSE servers in both its IDE extension and CLI.
Separate ownership
Use Hronaut when a named browser workspace should be owned by a separate desktop app and remain available after a task finishes.
Human handoff
Watch Hronaut, pause MCP before a sensitive step, interact manually, then resume an agent in the same workspace.
Explicit Streamable HTTP setup
Start Hronaut first. In Cline's MCP panel, add a remote server, choose Streamable HTTP, and enter the endpoint. Or add the same definition through cline mcp. Set the type explicitly: Cline preserves an untyped URL as legacy SSE for backward compatibility. Official Cline MCP setup ↗
Authentication disabled
{
"mcpServers": {
"hronaut": {
"type": "streamableHttp",
"url": "http://127.0.0.1:47812/mcp",
"disabled": false,
"autoApprove": []
}
}
}Keep autoApprove empty while verifying the connection. The Cline CLI wizard accepts the same server name, transport, and URL.
Authentication enabled
Enable Require MCP authentication in Hronaut, then copy the generated configuration from Hronaut Home and retain the explicit streamableHttp type. Do not commit or paste the owner token into chat.
Verify before using a login
Open Cline's MCP Servers panel, or run cline config mcp --json, and confirm hronaut is enabled. The interactive manager is cline mcp.
Leave MCP auto-approval disabled until the server and tool list match what you expect.
Ask: “Create a Hronaut workspace named first-check, open https://example.com inside it, and tell me the page title and workspace ID. Do not use my Default workspace.”
A separate visible first-check workspace opens Example Domain, and Cline reports its stable workspace ID.
Security boundary
A new Hronaut profile starts without MCP authentication for simple local setup. Before using valuable signed-in sessions, enable Require MCP authentication. Websites can contain prompt injection, so review surprising MCP calls and pause MCP before entering passwords, security keys, payment details, or other human-only information.
Choose deliberately
The distinction is lifecycle ownership, not whether Cline can automate a browser. Hronaut adds a separately managed local desktop boundary, named workspaces, and explicit human controls.
Last verified against Cline's official MCP and browser lifecycle documentation on August 27, 2026.