Local MCP endpoint

http://127.0.0.1:47812/mcp

Cloud agents cannot reach this computer's loopback endpoint. Cascade and Hronaut must run on the same computer.

Choose the right instructions

This page is for the legacy Cascade agent.

Current Devin Desktop documentation says Devin Local is the default agent for new Devin Desktop tabs. It uses Devin CLI configuration instead of the Windsurf-era Cascade file. For a new tab, follow the Devin Local browser MCP guide. Continue here only when the interface identifies the agent as Cascade.

Desktop Cascade setup

Add Hronaut as a user-level URL server.

Open Cascade's MCP settings and edit ~/.codeium/windsurf/mcp_config.json. The entry is available across local projects.

Authentication disabled

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "hronaut": {
      "serverUrl": "http://127.0.0.1:47812/mcp"
    }
  }
}

Open Cascade → MCPs, refresh the server list, and confirm hronaut is connected.

Authentication enabled

Read the owner token from its file

Enable Require MCP authentication in Hronaut, then copy the generated Windsurf entry from Hronaut Home. Cascade supports file interpolation, so the secret can stay out of JSON.

{
  "mcpServers": {
    "hronaut": {
      "serverUrl": "http://127.0.0.1:47812/mcp",
      "headers": {
        "Authorization": "Bearer ${file:/path/from-hronaut-home}"
      }
    }
  }
}

Do not commit the resolved token, paste it into chat, or expose the owner-token file to another user.

Windsurf plugin for JetBrains

Use the plugin's separate configuration file.

The Windsurf plugin for JetBrains documents the file ~/.codeium/mcp_config.json. Open Settings → Tools → Windsurf Settings → Add Server and use the same serverUrl entry. Its published guide documents environment interpolation but not token-file interpolation, so use the exact authenticated snippet Hronaut Home offers for your client rather than inventing a secret format.

Observable verification

Verify the connection in Hronaut and Cascade.

1 · Client state

Refresh MCP servers

Confirm hronaut appears connected in Cascade's MCP panel. A saved JSON file alone is not runtime proof.

2 · Hronaut state

Watch Connections

Open Hronaut Home and confirm the client appears under Connections.

3 · Browser task

Create an isolated workspace

Ask Cascade: “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.”

Expect a visible first-check workspace showing Example Domain.

Security and reachability

Local browser control stays local.

Hronaut listens on loopback. Only a local client on the same computer can connect without additional networking. Authentication is off for a new Hronaut profile, so any process running as your user can control it. Enable authentication for sensitive signed-in profiles and keep the owner-token file private.

Use named workspaces for agent tasks and review actions against authenticated websites. Hronaut does not turn a local agent into a safe unattended credential broker.

Primary sources

Configuration and migration evidence.

Keep the browser; change the task

Use a named Hronaut workspace for every durable browser job.

Named workspaces isolate cookies and storage from the human Default workspace while remaining available to the next local agent task.