nyrn
/
openclaw
mirror of https://github.com/openclaw/openclaw.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
openclaw/assets/chrome-extension
History
stone-jin 04b3a51d3a fix(browser): preserve debugger attachment across relay disconnects during navigation reattach 2026-03-02 06:38:21 +00:00
..
icons feat: polish chrome extension UX 2026-01-15 05:11:03 +00:00
README.md fix(browser): unify extension relay auth on gateway token 2026-02-19 08:40:40 +01: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 fix(browser): preserve debugger attachment across relay disconnects during navigation reattach 2026-03-02 06:38:21 +00:00
manifest.json fix(browser): harden extension relay worker recovery 2026-02-22 19:08:38 +01:00
options-validation.js refactor(browser): share relay token + options validation tests 2026-02-24 04:23:22 +00:00
options.html fix(browser): unify extension relay auth on gateway token 2026-02-19 08:40:40 +01:00
options.js refactor(browser): share relay token + options validation tests 2026-02-24 04:23:22 +00: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

  1. Build/run OpenClaw Gateway with browser control enabled.

  2. Ensure the relay server is reachable at http://127.0.0.1:18792/ (default).

  3. Install the extension to a stable path:

    openclaw browser extension install
openclaw browser extension path

  4. Chrome → chrome://extensions → enable “Developer mode”.

  5. “Load unpacked” → select the path printed above.

  6. 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).