@agent-browser/chrome-extension-provider

Optional Chrome extension bridge provider for agent-browser.

This package lets agent-browser connect to the user's already running desktop Chrome through an unpacked MV3 extension. It exposes a browser.provider plugin that returns a local CDP WebSocket URL, while the bridge daemon translates CDP traffic to the extension's chrome.debugger transport.

Install

pnpm add @agent-browser/chrome-extension-provider

Build the package if you are using it from a workspace checkout:

pnpm --filter @agent-browser/chrome-extension-provider build

Load the unpacked extension from:

packages/@agent-browser/chrome-extension-provider/.output/chrome-mv3

Configure agent-browser

Add the provider plugin:

{
  "plugins": [
    {
      "name": "chrome-extension",
      "command": "agent-browser-plugin-chrome-extension",
      "capabilities": ["browser.provider", "command.run", "chrome-extension.manage"]
    }
  ]
}

Then run:

agent-browser --provider chrome-extension open https://example.com
agent-browser snapshot -i

Status

Use the management command to see whether the daemon and extension profiles are connected:

agent-browser plugin run chrome-extension chrome-extension.status

The status output includes the unpacked extension path, bridge protocol version, daemon port, connected profile ids, extension id, and current tabs.

Configuration

The extension connects to port 19826 by default. For a custom port, set chrome.storage.local.bridgePort or chrome.storage.local.bridgePorts in the extension profile to match AGENT_BROWSER_CHROME_BRIDGE_PORT.

Limits

The MVP targets ordinary web pages in desktop Chrome 120 or newer. It does not support chrome:// pages, browser UI pages, automation of other extension pages, Chrome Web Store distribution, Native Messaging bootstrap, or capabilities that are already incomplete for external CDP sessions such as some recording flows.