@panerelay/browser-use

Use the browser-use CLI, CLI MCP, and native helpers with your existing signed-in Chrome session. Choose the current tab for focused work or all supported web tabs for cross-page workflows; Panerelay keeps active control separately visible and releasable without enabling Chrome Remote Debugging or exporting login state.

This is an opt-in automation tool integration and a peer of agent-browser. It does not replace or modify browser-use.

Before you start

• Install the official Panerelay Extension in Chrome.
• Install Node.js 20 or newer.
• Install browser-use 0.13.7 or newer with Browser Harness 0.1.8 or newer by following the upstream CLI instructions.

Panerelay setup verifies browser-use but does not install, upgrade, downgrade, rewrite, or add it to PATH.

Set up with your Agent

Install the unified Skill, then ask your Agent to use its Browser Use workflow:

npx skills add https://github.com/F-loat/panerelay --skill panerelay

The Skill defines environment inspection, official upstream installation when needed, Panerelay integration, the user authorization stop, verification, and troubleshooting.

Set up manually

After browser-use --help confirms that the CLI is available, install and diagnose the Panerelay integration. Setup probes the installed browser-use and Browser Harness package versions directly and stops if they are unsupported:

npx --yes @panerelay/setup --browser-use
npx --yes @panerelay/setup doctor --browser-use

Open Panerelay in Chrome and choose current-tab or all-supported-tabs authorization for the task. Re-run the doctor command and require the browser-use compatibility and Extension-connection checks to pass.

Then use the official Browser Use CLI with the fixed Panerelay discovery URL. This works even when Extension mode is not saved as the default:

BU_CDP_URL=http://127.0.0.1:43827/cdp/browser-use browser-use <<'PY'
print(list_tabs())
PY

PowerShell:

$env:BU_CDP_URL = 'http://127.0.0.1:43827/cdp/browser-use'
@'
print(list_tabs())
'@ | browser-use

Command Prompt:

set "BU_CDP_URL=http://127.0.0.1:43827/cdp/browser-use"
echo print(list_tabs()) | browser-use

Success means the command lists only tabs authorized in Panerelay.

Browser Harness environment

In Extension mode, setup manages Browser Harness's user-scoped environment file and writes the fixed discovery URL below:

BU_CDP_URL=http://127.0.0.1:43827/cdp/browser-use

You normally do not need to set this variable yourself. browser-use and browser-use --cli-mcp read it directly. The URL is a stable loopback discovery endpoint, not a permanent CDP credential: Panerelay selects the configured browser and creates a short-lived connection behind it for each Browser Harness daemon. Do not copy or persist the dynamic WebSocket/bootstrap URL returned during discovery.

The explicit BU_CDP_URL= prefix is a one-process override. After saving Extension mode, it can be omitted. Do not set Browser Harness's higher-priority BU_CDP_WS at the same time; it takes precedence over BU_CDP_URL.

Use the base CLI to change the durable mode:

panerelay connection use browser-use extension  # manage BU_CDP_URL
panerelay connection use browser-use direct     # remove Panerelay-managed Browser Harness keys

The managed environment file is the default for new Browser Use processes. An explicitly supplied process environment still takes precedence for that process.

What setup adds

Setup adds only Panerelay-owned integration files:

• a protected Browser Use adapter registration and internal adapter launcher (it does not replace the official browser-use command);
• a saved Direct or Extension connection preference and managed Browser Harness environment file.

The official browser-use executable remains the user-installed command. This package supplies its connection environment and is not intended to be invoked directly by Agents.

Supported surfaces

| Surface | Support | | --- | --- | | Official browser-use CLI with setup-managed environment | Supported | | Browser Use workflow in the independent panerelay Skill | Supported | | Official browser-use --cli-mcp | Supported | | Saved Direct or Extension mode and one-run override | Supported | | Arbitrary browser-use Python SDK construction | Not transparently intercepted; requires explicit connection integration |

Runtime boundary

Extension mode exposes the scope selected in Panerelay: the current tab or all supported web tabs. Unsupported browser-wide, whole-profile, isolated-context, and top-level containment operations fail explicitly.

A private browser-use daemon persists across sequential commands and shares its current-page state; it is not per-Agent task isolation. Simultaneous canonical runs are serialized or fail busy. User release, authorization loss, Extension or Native Host disconnection, and WebSocket loss remove browser authority even if the detached upstream process remains alive.

New Side Panel conversations may inject the originating opaque target UUID. Keep the existing BU_NAME=panerelay lane, call the supplied switch_tab(targetId), and verify with page_info() before acting. This uses Browser Harness's existing exact target selector; Panerelay does not start a per-conversation daemon or fall back to Direct mode, another browser, or URL/title matching when the target is unavailable.

Compatibility

browser-use 0.13.7 is the supported minimum. The exact verified baseline is browser-use 0.13.7 with Browser Harness 0.1.8. Newer supported versions meet the version floor but do not automatically inherit Verified status.

• Upstream browser-use CLI documentation
• Upstream browser-use CLI MCP documentation
• Panerelay browser-use 0.13.7 compatibility record
• @panerelay/setup technical reference