Why Browser-Native Beats Plugins Every Time

Heavy browser plugins are sandboxed, rate-limited, and constantly breaking. Biome's browser relay takes a lighter path: a small Chrome companion for connection setup, and a local relay for the automation work. Here's why that distinction matters for AI automation.

The plugin trap

Heavy browser extensions run in a sandbox with restricted DOM access, rate-limited messaging APIs, and permissions that individual sites can refuse. When a target site updates its markup, brittle automation breaks. When Chrome updates its extension manifest rules, every oversized extension has more surface area to maintain.

Maintaining a scraping or automation plugin is whack-a-mole by design. The extension model was built for adding UI to web pages — not for carrying the whole browser automation layer.

How the relay works

Biome's browser relay is a lightweight local process that runs alongside the macOS app. A small Chrome companion helps the app discover and coordinate browser sessions, while the relay keeps the automation work local. This means fuller tab visibility, reliable click simulation, and form access without turning the extension itself into the automation engine.

The important part is where the control lives: not in a fragile pile of content scripts, but in a local relay designed for programmatic browser work.

Resilience by default

Because the relay talks to the browser at the protocol level rather than the DOM level, it doesn't care if a site redesigns its buttons or renames its CSS classes. The agent targets elements by role and semantic position, not by brittle selectors that expire on the next deploy.

This is the fundamental architectural difference between browser automation that works reliably and automation that requires constant babysitting.

What this unlocks

Your agent can draft a Linear ticket while reading a Slack thread, cross-reference a code review with a Notion doc, and send a calendar invite from Gmail — all in one task, without you switching tabs. That kind of multi-site orchestration is impossible inside the extension model, where each tab is an isolated sandbox with no shared state.

The relay is included in Biome for macOS and requires no additional setup beyond the initial browser connection in Preferences → Browser Control. Browser Control is a Pro feature — the relay itself ships in every build.