HRONAUT
Download

Qwen Code browser MCP

Give Qwen Code a browser that survives the terminal task.

Hronaut runs a separate visible Chromium application. The local Qwen Code process connects through native Streamable HTTP MCP while named workspaces, sign-ins, tabs, and debugging state remain available after one Qwen session ends.

Connect Qwen CodeDownload HronautCompare browser tools

Hronaut is an independent project and is not affiliated with or endorsed by Alibaba Cloud or the Qwen team.

Local MCP endpoint

http://127.0.0.1:47812/mcp

This guide is for Qwen Code running on the same computer as Hronaut. Qwen Chat and remotely executed Qwen sessions cannot reach this computer's loopback endpoint.

Official local agent

Install Qwen Code, then verify the CLI.

Qwen Code is an Apache-2.0 open-source coding agent for terminals, IDEs, and desktop. The npm package is the most portable installation path; the official repository also publishes standalone and Homebrew options.

Node.js 22 or newer

Install and verify

npm install -g @qwen-code/qwen-code@latest
qwen --version

These are the current commands published by the official Qwen Code repository ↗.

User-level setup

Add Hronaut through Qwen Code's native HTTP transport.

Start Hronaut first. The explicit --scope user keeps the server in ~/.qwen/settings.json across repositories instead of trusting a project-controlled settings file.

Authentication disabled

Add the loopback server

qwen mcp add --scope user --transport http hronaut http://127.0.0.1:47812/mcp

This command intentionally contains no credential. A new Hronaut profile starts with MCP authentication disabled.

Equivalent user configuration

~/.qwen/settings.json

{
  "mcpServers": {
    "hronaut": {
      "httpUrl": "http://127.0.0.1:47812/mcp",
      "trust": false
    }
  }
}

Authentication enabled

Keep the bearer value out of JSON

{
  "mcpServers": {
    "hronaut": {
      "httpUrl": "http://127.0.0.1:47812/mcp",
      "headers": {
        "Authorization": "Bearer ${HRONAUT_MCP_TOKEN}"
      },
      "trust": false
    }
  }
}

Enable Require MCP authentication in Hronaut and export HRONAUT_MCP_TOKEN in the shell that starts Qwen Code. Copy the owner token from trusted Hronaut Home UI; do not paste it into JSON, a project file, chat, screenshots, or shell history. Qwen Code 0.16.0 had a fixed environment-loading bug for values present only in .env, so a process environment variable is the most compatible path.

Observable verification

Inspect discovery, then prove browser behavior.

1 · Configuration

List the saved server

qwen mcp list

Start qwen, enter /mcp, and confirm that hronaut exposes tools. Restart an already-running Qwen session after changing configuration.

2 · Runtime

Watch both status surfaces

Qwen Code displays an MCP readiness indicator while discovery runs. Open Hronaut Home and confirm Qwen Code appears under Connections before asking it to browse.

3 · Browser task

Create an isolated workspace

Ask: “Using Hronaut, create a 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.

Local reachability and approval

Keep browser authority visible, scoped, and local.

Leave "trust": false so Qwen Code asks before using Hronaut tools. Its documentation warns that trust: true bypasses per-server confirmations in a trusted workspace; do not enable it for unfamiliar repositories or prompts.

A new Hronaut profile starts without authentication, so any process running as your user can control it. Enable authentication for sensitive browser profiles and pause MCP before entering passwords, security keys, payment details, or other human-only information.

Qwen Chat and remote/cloud runtimes execute outside this desktop boundary. Do not expose or tunnel Hronaut to make those surfaces reach 127.0.0.1; run Qwen Code locally instead.

Primary sources

Installation, HTTP transport, and permission 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 Qwen Code task—or another compatible local MCP client.

Download HronautAll client setupSafe login handoff