@panerelay/cli

Recurring browser-authenticated Fetch, site-adapter, and browser-selection commands for Panerelay.

Base Setup installs or updates the global panerelay command. Install site adapters separately when needed:

npx --yes @panerelay/setup
npx --yes @panerelay/setup add bilibili
panerelay browsers
panerelay browser use edge

Browser-backed fetch

The persistent CLI can issue Fetch-shaped requests through one selected live Panerelay Extension:

panerelay fetch https://api.example.com/me \
  -H 'Origin: https://www.example.com' \
  -H 'Referer: https://www.example.com/' \
  --response json

Supported raw options are --method, repeatable --header/-H, repeatable --query, --data, --data-base64, --response, --timeout, --cookies, --no-cookies, and --browser. The output is a structured JSON object containing HTTP status, headers, decoded body type, final URL, redirect state, and attached-cookie count. Browser cookies are included by default but never printed or passed through the Bridge protocol as header material. Redirects always fail closed.

Origin and Referer are customizable. When omitted they default to the target origin and <origin>/panerelay; an explicit empty value removes the generated header. The target still needs a Panerelay domain grant and Chrome site access. Raw CLI execution does not open permission UI automatically, so a missing grant or Chrome rejection returns bounded guidance to authorize and retry.

Fetch adapters installed by @panerelay/setup use an OpenCLI-like form:

panerelay fetch --help
panerelay fetch bilibili --help
panerelay fetch bilibili me
panerelay fetch bilibili me --json
panerelay fetch bilibili subtitle BV1xx411c7mD --lang zh-CN
panerelay fetch bilibili comment BV1xx411c7mD 'test' --execute

Help reads only protected manifest metadata and does not select a browser. Adapter results use an OpenCLI-style table with an item-count and one-decimal elapsed-time footer by default; like OpenCLI, timing starts when the concrete command action begins and stops before rendering. --json prints only the underlying structured result for scripts. Execution verifies the registered digest and runs the adapter once in a bounded child process with a short-lived fetch-only token. Raw requests receive one exact-origin session; adapters receive only the origin and protected binding authority declared in their installed manifest. The Bridge and Extension enforce that authority independently. Fetch still creates no tab-control lease.

The built-in Bilibili command inventory is whoami, me, video, search, hot, ranking, dynamic, feed, feed-detail, favorite, history, following, user-videos, comments, subtitle, summary, comment, follow, and unfollow. The final three are writes. Comment requires --execute; each write selects a protected manifest binding that asks the Extension to inject bili_jct as the csrf form field without disclosing its value to the adapter. Interactive login and media/filesystem-oriented download are excluded.

The installed Native Host also supports a bounded stdio MCP mode used by Panerelay's Codex/Claude integrations. It exposes one browser_fetch tool with the same exact-origin, permission, Cookie, timeout, redirect, response, cancellation, and non-disclosure boundaries. It is a request tool rather than browser automation or a search engine. Arbitrary Cookie names and browser storage keys are not MCP inputs.

Once <site> <command> has been parsed, manifest-declared --lang remains a command argument. A global CLI locale must appear before fetch, such as panerelay --lang zh-CN fetch bilibili --help.

The CLI lists live Panerelay browser registrations and manages the saved routing default. It does not install or control an automation engine, grant site access, authorize tabs, or change control leases. Browser automation remains the responsibility of integrations such as agent-browser or browser-use.

Use @panerelay/setup for one-time installation, diagnostics, updates, and uninstall.

Setup-managed connection adapters can also expose engine-neutral mode preferences. Browser Use itself is invoked through the official browser-use command; Setup manages its Browser Harness environment default:

panerelay connection use browser-use extension
panerelay connection use browser-use direct

The CLI does not interpret browser-use automation. The saved mode controls the managed Browser Harness environment file. In Extension mode it contains:

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

The official browser-use and browser-use --cli-mcp commands read this variable directly. It is a fixed loopback discovery URL; Panerelay still selects the saved browser and creates short-lived CDP credentials behind it. Extension-mode browser-use uses a user-scoped concurrency lane; sequential processes share the upstream daemon state, while overlapping runs wait briefly or fail explicitly as busy. Direct mode removes Panerelay-managed Browser Harness keys.