HRONAUT
Download

Kilo Code browser MCP

Give Kilo Code a browser that survives the task.

Hronaut runs a separate visible Chromium application. Local Kilo Code IDE and CLI sessions connect over loopback MCP while named browser workspaces remain available after one task ends or another compatible local MCP client takes over.

Connect Kilo CodeDownload HronautCompare browser tools

Hronaut is an independent project and is not affiliated with or endorsed by Kilo Code.

Local MCP endpoint

http://127.0.0.1:47812/mcp

Hronaut listens on loopback. It works with a Kilo Code IDE or CLI running on the same machine; it is not a hosted browser for remote agents.

Use the built-in option when it fits

Kilo Code already has built-in browser automation powered by Playwright.

Kilo Code's browser-use feature launches a browser for a task, shows screenshots in the conversation, and closes when the task finishes. That is a good fit for disposable task automation. Use Hronaut when the browser should be owned by a separate desktop app and remain available beyond that task. Official Kilo Code browser-use guide ↗

Built-in browser

One disposable task

Use browser use when Kilo Code should create and clean up temporary browser machinery within one task.

Kilo Code MCP

Local IDE and CLI tools

Kilo Code's shared configuration supports remote MCP servers for its local IDE, CLI, and JetBrains surfaces.

Separate ownership

Beyond one task or client

Use Hronaut when a named browser workspace should stay visible and durable independently of one Kilo Code task.

Human handoff

Pause and take over

Watch Hronaut, pause MCP before a sensitive step, interact manually, then resume an agent in the same workspace.

Current cloud boundary

This setup is for local Kilo Code clients.

Cloud Agent MCP support is currently documented as coming. A loopback URL exists only on the machine where Hronaut is running, so this configuration does not make a current Kilo Cloud Agent a remote control for your desktop. Re-check Kilo Code's capability page before assuming that boundary has changed. Official Kilo Code Cloud Agent guide ↗

Global local-client setup

Add Hronaut to Kilo Code's shared configuration.

Start Hronaut first. Add the server under the top-level mcp key in ~/.config/kilo/kilo.jsonc. The global file is shared by Kilo Code IDE, CLI, and JetBrains clients. Official Kilo Code MCP setup ↗

Authentication disabled

~/.config/kilo/kilo.jsonc

{
  "$schema": "https://app.kilo.ai/config.json",
  "mcp": {
    "hronaut": {
      "type": "remote",
      "url": "http://127.0.0.1:47812/mcp",
      "enabled": true,
      "oauth": false
    }
  }
}

Set oauth to false because Hronaut does not use OAuth discovery. This snippet intentionally contains no bearer token.

Authentication enabled

Copy the current protected setup

Enable Require MCP authentication in Hronaut, then use the current token-aware client configuration shown by Hronaut Home. Keep the owner token in its protected file; do not paste it into chat, issues, screenshots, or source control.

Verify before using a login

Prove the connection in an isolated Hronaut workspace.

  1. 1

    Confirm server discovery

    Run kilo mcp list and confirm hronaut is enabled. kilo mcp debug hronaut can help diagnose transport or OAuth configuration, but a successful browser action is the stronger end-to-end check. Official Kilo CLI reference ↗

  2. 2

    Keep approval on

    Review the MCP server and its tool list before allowing calls automatically.

  3. 3

    Create a clean first workspace

    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.”

  4. 4

    Confirm the observable result

    A separate visible first-check workspace opens Example Domain, and Kilo Code reports its stable workspace ID.

Security boundary

Treat a persistent browser as durable authority.

A new Hronaut profile starts without MCP authentication for simple local setup. In that mode, any process running as your user can control the browser profile. 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

Use Kilo Code's browser for a disposable task. Use Hronaut for a browser workspace that survives it.

The distinction is lifecycle ownership, not whether Kilo Code can automate a browser. Hronaut adds a separately managed local desktop boundary, named workspaces, and explicit human controls.

Last verified against Kilo Code's official MCP, browser-use, CLI, and Cloud Agent documentation on August 27, 2026.

Choose a desktop packageAll client setupSafe login handoffInspect the source