#How fix browser-use??

1 messages · Page 1 of 1 (latest)

cinder egret
#

Hi everyone! 👋

I've been trying to get the Browser Relay / Chrome extension working with my OpenClaw setup, but I'm running into some issues and would love some guidance.

Current situation:

• Port 18792 (Browser Relay) doesn't appear to be running at all
• There's no relay config section in my openclaw.json
• I couldn't find any documentation on how to set it up
• GitHub issue #24387 seems to still be open

I'm currently on version 2026.3.1 and I see the latest is 2026.5.15.

My questions:

  1. Is there a way to manually enable/configure the Browser Relay in openclaw.json?
  2. Has the relay issue been addressed in the latest release?
  3. Is upgrading to 2026.5.15 recommended at this point?

I tried using the HMAC-derived token workaround mentioned in issue #24387, but the relay server itself doesn't seem to be listening on port 18792, so the extension still can't connect.

Any help would be greatly appreciated! Thanks in advance 🙏

balmy capeBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

storm flareBOT
# cinder egret Hi everyone! 👋 I've been trying to get the Browser Relay / Chrome extension wo...

I checked current docs/source. Short version: the Chrome extension relay path is legacy now. In current OpenClaw, browser.relayBindHost is removed and old browser.profiles.*.driver: "extension" gets migrated to "existing-session" by openclaw doctor.

So for your questions:

  1. I would not manually add a Browser Relay section. Current config uses browser profiles, usually either the managed openclaw profile or existing-session for attaching to your real signed-in Chrome/Brave/Edge.
  2. Issue #24387 is closed, but the newer path is not “make port 18792 work”; it’s the Chrome MCP existing-session attach model. The source also marks 18792-18799 as reserved for future one-off services, while managed browser CDP profiles use 18800+ and the browser control service is derived from the gateway port, default 18791.
  3. Yes, I’d upgrade from 2026.3.1 to current, then run the migration/health checks.

Suggested sequence:

openclaw --version
openclaw doctor
openclaw browser profiles
openclaw browser --browser-profile openclaw start
openclaw browser --browser-profile openclaw tabs