§ Browser Extension

The Hive Browser Bridge

A Chrome extension that lets Hive's AI subagents drive the browser you're already signed in to — in visible, isolated tab groups you can watch live.

v1.2.397 users★ 5.0Updated May 2026

Agents work in the same browser the user is already signed in to — so they inherit existing logins and sessions, and the user can watch the work happen live in their own tab bar.

§01 Why it exists

The problem with headless browsers.

Without the extension, every agent spins up its own isolated Chrome process over CDP. That model has real costs.

No sessions

A fresh Chrome process has none of the user's logins, so agents hit auth walls on sites the user is already signed in to.

Invisible

Work happens in a window the user can't see, so they can't follow along or step in when an agent goes off track.

Heavy

One Chrome process per agent is resource-hungry, especially during multi-agent fan-out across a colony.

The extension replaces that model: one browser, the user's own, with each agent confined to its own tab group.

§02 How it works

One bridge, one socket,
one browser.

The Hive app runs a local bridge server. The extension connects to it over a WebSocket and executes commands using Chrome's own extension APIs.

Hive app
GCU MCP Server (Python)
Runs the local bridge server that agents talk to.
Chrome extension
background.js + offscreen.js
Receives commands and executes them in the browser.
Endpoint
Your existing Chrome browser
Already signed in, already running — nothing new launches.
offscreen.js

Hosts the persistent WebSocket. It lives in an offscreen document so the connection survives Chrome suspending the service worker.

background.js

Receives commands from the bridge, executes them via Chrome extension APIs, and returns results.

A tab group per subagent

When an agent starts, the bridge sends context.create and the extension opens a new chrome.tabGroups entry for it — colour-coded and labelled in your tab bar, isolated from your own tabs. The agent drives tabs inside that group via the Chrome DevTools Protocol. When the agent stops, context.destroy closes only that group's tabs — Chrome itself stays running.

§03 Health side panel

Know the link is live
at a glance.

Clicking the toolbar icon opens a side panel that runs a fresh end-to-end diagnostic every ~2 seconds — it holds no cached “connected” flag, so it cannot get stuck green on a dead link.

Hive app

The bridge answers on http://127.0.0.1:14830.

Browser bridge

The bridge server inside the app is running.

WebSocket

The socket's live readyState — open, connecting, or closed.

Extension link

The bridge accepted this specific extension instance.

Heartbeat

Two-way round-trip freshness; a half-open socket is detected and auto-reconnected.

Debugger

Warns when DevTools or another tool holds chrome.debugger on a tab and blocks automation.

The panel also lists active agents — one row per live tab group — so you can see which colony workers are driving the browser right now.

§04 Get the extension

Install in one click.

Add the Hive Browser Bridge from the Chrome Web Store. It updates automatically — there's nothing else to set up.

Add to ChromeChrome Web Store · Free
v1.2.397 users★ 5.0Updated May 2026
§05 Troubleshooting

When something looks wrong.

Check the side panel first — each row points to a specific fix.

"Hive app" shows red
The Hive app isn't running, or the bridge server failed to start. Restart the app.
WebSocket red but Hive app green
The extension lost its socket. It auto-reconnects every ~2s; if it stays red, reload the extension at chrome://extensions.
"Extension link" shows red
The bridge is bound to a different browser instance. Make sure only one Chrome profile has the extension active.
Everything green but automation stalls
Check the Debugger row — DevTools or another tool is holding chrome.debugger on the tab. Close DevTools on that tab.