Local browser bridge

Chrome Relay

Let local coding agents drive the Chrome session you already have open — tabs, cookies, and logged-in apps stay on your machine.

Add to Chrome Install the CLI

For the browser you actually use.

Headless automation is fine for CI. Chrome Relay is for when your agent needs the tab already open on your desktop — SSO, extensions, local dev servers, real profile state.

The extension talks only to a local native host. No cloud account, no telemetry, no remote relay.

Chrome Relay popup showing a CLI command and recent local tool executions

Install

Add the extension, then register the local native host.

  • Native messaging pinned to the Chrome Relay extension IDs.
  • Local HTTP bridge on 127.0.0.1, rejects browser-origin requests.
  • Only the last few tool summaries are stored — in Chrome local storage.
$ pnpm add -g chrome-relay
$ chrome-relay install
$ chrome-relay doctor

$ chrome-relay tabs
$ chrome-relay read -i

How it works

  1. Extension

    Runs in Chrome, acts on tabs only when your local agent asks.

  2. Native host

    The chrome-relay CLI registers Chrome native messaging locally.

  3. Tools

    List tabs, navigate, click, fill, send keys, read pages, screenshot.

  4. Local only

    Traffic moves between Chrome, the host, and your CLI — on-device.