BROWSER FETCH · EXISTING-BROWSER CONNECT

Browser login state. Ready for your Agents.

Fetch signed-in APIs, or connect agent-browser Browser Use Playwright CLI agent-browser agent-browser · Browser Use · Playwright CLI to existing tabs.

Add Panerelay

See installation steps

Cookies stay in the browser
Domain or tab approval
Visible, releasable control

PANERELAY QUICKSTART

Control released

Panerelay Bridge offline

Install Panerelay + Agent Skill

Setup provides the CLI. One Skill guides Fetch and Connect workflows.

Fetch known URLs with browser login state Connect automation to authorized tabs

Run Setup + install Skill

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

CLI + Skill ready

✓ panerelay command + Skill ready

A Your Agent Panerelay setup

agent-browser browser-use Playwright CLI

Use the panerelay Skill. Set up agent-browser, run doctor, and stop when I need to authorize a tab.

✓Found agent-browser 0.33.0 $npx --yes @panerelay/setup --agent-browser $npx --yes @panerelay/setup doctor --agent-browser ✓Panerelay is ready · tab authorization required

AGENTCONNECTED

$agent-browser --provider panerelay tab list →t1 · Project board $agent-browser --provider panerelay snapshot -i →observing 1 · controlling 0 $agent-browser --provider panerelay click @e4 ✓Found 2 issues blocking release

Project board 1

⌁

EXTERNAL CONTROL agent-browser · quickstart Active · 1 controlled tab · Heartbeat live

Read page · done Interact with page · done

Panerelay Connected

Browser access Authorized: Project board Release

This tab All tabs

⌁

EXTERNAL CONTROL agent-browser · quickstart Released · 0 controlled tabs

✓

Control released

This tab remains authorized. Click the selected scope separately to cancel authorization.

Your signed-in browser Fetch or Connect Explicit authorization

01 · WHY PANERELAY

Use the browser state
you already have.

Fetch authenticated endpoints or connect automation tools without exporting cookies, creating another profile, or turning on remote debugging.

Fetch as the signed-in browser

Send bounded requests to known URLs while cookies remain inside the Extension.

Connect existing tabs

Use agent-browser, Browser Use, or Playwright CLI on only the tabs you authorize.

Keep authority explicit

Fetch domains, tab scope, and active control stay separate and user-controlled.

02 · SETUP

Install once.
Then ask for Fetch or Connect.

01
EXTENSION
Add Panerelay to Chrome or Edge.

Install the official Chrome Web Store build. Edge may first ask you to allow extensions from other stores.
Open Chrome Web Store
02
SETUP + AGENT SKILL
Install Panerelay, then one Skill for every workflow.

Base Setup installs the Native Host and global CLI. The Skill separately guides browser-authenticated Fetch, Agent routing, setup, verification, and troubleshooting.

Setup provides the command; one Skill guides every workflow.
npx --yes @panerelay/setup

npx skills add https://github.com/F-loat/panerelay --skill panerelay
USE FETCH Give your Agent a known URL.
1. 01
  Share the exact HTTP(S) URL you want to request.
2. 02
  Ask the Agent to use Panerelay Fetch with your browser login state.
3. 03
  Approve that exact domain in the Extension when asked.
Use the installed panerelay Skill and Panerelay Fetch to request https://api.example.com/me with my browser login state.
Browser

Bridge

Agent
✓
APPROVAL
Approve only what the task needs.

Fetch asks for a domain. Connect asks for the current tab or all supported tabs. Active control remains visible and releasable.
Read advanced management

03 · FETCH × CONNECT

Two browser capabilities.
One local boundary.

Use Fetch for known HTTP(S) requests. Use Connect for rendered pages and interaction.

FETCH

Request known URLs
with browser login state.

Run Setup once, approve the exact domain, then request an absolute URL. Cookies stay inside the Extension and redirects fail closed.

Fetch handles exact URLs. Use Connect for DOM, navigation, screenshots, or clicks.

terminal

# Install the Host and global CLI once
$ npx --yes @panerelay/setup

# Approve the exact domain, then request an absolute URL
$ panerelay fetch --authorize api.example.com
$ panerelay fetch https://api.example.com/me \
  --response json
✓ 200 OK · browser session attached

# Optional: install and use a site adapter
$ npx --yes @panerelay/setup add bilibili
$ panerelay bilibili me

CONNECT

Keep your automation engine.
Connect it to existing tabs.

agent-browser, Browser Use, and Playwright CLI keep their own automation semantics. Panerelay supplies the authorized connection to your existing browser.

Explicit integration

Connect agent-browser to your everyday tabs.

Let CLI- or MCP-capable Agents use agent-browser on the current tab or all supported tabs. Native snapshots, refs, screenshots, network tools, and diagnostics stay intact.

Works with shell-capable Agents
Background automation does not steal visible tab focus
Current profile and login state stay in the browser

Read the agent-browser quickstart Compatibility evidence

terminal

# See the tabs you authorized
$ agent-browser \
  --provider panerelay tab list

→ t1  Project board
→ t2  Pull request · Panerelay

# Work without switching your visible tab
$ agent-browser --provider panerelay \
  --session research snapshot -i

Explicit integration

Connect browser-use
to your signed-in Chrome.

The browser-use CLI and CLI MCP keep their normal workflow. Panerelay routes Browser Harness to the tab scope you select in your existing Chrome—without remote debugging or exported login state.

Browser Harness-backed CLI and CLI MCP in the unified Skill
Persistent private lane with visible release
Arbitrary Python SDK construction is outside this transparent path

Read the browser-use CLI docs Compatibility evidence

browser-use CLI · Browser Harness

# Browser-use helpers through Panerelay
$ BU_CDP_URL=http://127.0.0.1:43827/cdp/browser-use browser-use <<'PY'
print(list_tabs())
PY
→ Existing Chrome · authorized tabs

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

✓ Control visible · release stays available

Explicit integration

Connect Playwright CLI
to your everyday tabs.

Keep the upstream CLI and point it explicitly at Panerelay's Playwright CDP endpoint. Attach, tab selection, snapshots, and page evaluation stay in the normal Playwright CLI workflow.

Upstream attach, tab-list, tab-select, snapshot, and evaluation commands
Explicit Playwright endpoint with visible release
Panerelay does not replace the CLI or set a default connection

Read the connection notes Compatibility evidence

Playwright CLI

# Attach the upstream CLI explicitly
$ playwright-cli attach --cdp \
  http://127.0.0.1:43827/cdp/playwright
✓ Connected · authorized tabs only

$ playwright-cli tab-list
→ t1  Project board
$ playwright-cli tab-select t1

# Inspect the selected tab
$ playwright-cli snapshot

04 · TRUST BOUNDARY

Access is not focus.
Control is never invisible.

Panerelay separates Fetch domain approval, Connect tab authorization, and the live lease required for page mutation. Release ends active control without silently changing that scope.

Read the architecture RFCs

Fetch domain

Which origins may receive browser-backed requests.

Separate

Connect tabs

One current tab or all supported web tabs.

Flexible

Active control lease

Who may mutate right now—with release that preserves your scope.

Visible

Credentials stay in the browser.

Panerelay reuses your existing browser under the scope you select. It does not export cookies or log credentials, prompts, screenshots, page content, or request bodies by default.

No browser-process ownership.

Isolated profiles, launch-time proxy changes, and closing your browser remain outside an Extension-backed connection.

Compatibility, without hand-waving.

Exact evidence baselines: agent-browser 0.33.0, browser-use 0.13.7 with Browser Harness 0.1.8, and Playwright CLI 0.1.17. Edge remains Forwarded pending representative acceptance.

Chrome & Edge agent-browser 0.33.0 browser-use 0.13.7 Playwright CLI 0.1.17

OPEN SOURCE · MIT LICENSE

Keep your browser.
Fetch and Connect.

Install the Extension, run Setup, and add one Skill. Use Fetch for known URLs or Connect for browser automation.

Add Panerelay Star on GitHub

Browser login state. Ready for your Agents.

Use the browser stateyou already have.

Fetch as the signed-in browser

Connect existing tabs

Keep authority explicit

Install once.Then ask for Fetch or Connect.

Add Panerelay to Chrome or Edge.

Install Panerelay, then one Skill for every workflow.

Approve only what the task needs.

Two browser capabilities.One local boundary.

Request known URLswith browser login state.

Keep your automation engine.Connect it to existing tabs.

Connect agent-browser to your everyday tabs.

Connect browser-useto your signed-in Chrome.

Connect Playwright CLIto your everyday tabs.

Access is not focus.Control is never invisible.

Credentials stay in the browser.

No browser-process ownership.

Compatibility, without hand-waving.

Keep your browser.Fetch and Connect.

Use the browser state
you already have.

Install once.
Then ask for Fetch or Connect.

Two browser capabilities.
One local boundary.

Request known URLs
with browser login state.

Keep your automation engine.
Connect it to existing tabs.

Connect browser-use
to your signed-in Chrome.

Connect Playwright CLI
to your everyday tabs.

Access is not focus.
Control is never invisible.

Keep your browser.
Fetch and Connect.