History

Kriz Poon b7949d317f Chrome extension: simplify validation logic

Use OR operator to require both Browser and Protocol-Version fields. Simplified catch block to generic error message since specific wrong-port cases are already handled by the validation blocks above.

2026-02-24 04:16:08 +00:00

icons

feat: polish chrome extension UX

2026-01-15 05:11:03 +00:00

background-utils.js

fix(browser): derive relay auth token from gateway token in Chrome extension

2026-02-23 18:56:14 +00:00

background.js

Chrome extension: validate relay endpoint response format

2026-02-24 04:16:08 +00:00

manifest.json

fix(browser): harden extension relay worker recovery

2026-02-22 19:08:38 +01:00

options.html

fix(browser): unify extension relay auth on gateway token

2026-02-19 08:40:40 +01:00

options.js

Chrome extension: simplify validation logic

2026-02-24 04:16:08 +00:00

README.md

fix(browser): unify extension relay auth on gateway token

2026-02-19 08:40:40 +01:00

README.md

OpenClaw Chrome Extension (Browser Relay)

Purpose: attach OpenClaw to an existing Chrome tab so the Gateway can automate it (via the local CDP relay server).

Dev / load unpacked

Build/run OpenClaw Gateway with browser control enabled.
Ensure the relay server is reachable at http://127.0.0.1:18792/ (default).

Install the extension to a stable path:

openclaw browser extension install
openclaw browser extension path

Chrome → chrome://extensions → enable “Developer mode”.
“Load unpacked” → select the path printed above.
Pin the extension. Click the icon on a tab to attach/detach.

Options

Relay port: defaults to 18792.
Gateway token: required. Set this to gateway.auth.token (or OPENCLAW_GATEWAY_TOKEN).