Openclaw Browser relay extension

[vestal prairie]

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

[rich onyx]

Yeah, that AnswerOverflow thread is on the right track — there are two different tokens involved, and (depending on your OpenClaw version) the Chrome extension’s “Gateway token” field is misleading.

0) First: what version are you on?

Please run and paste:

openclaw --version

There are a couple versions where the relay behavior is buggy, and this helps avoid guessing.

---

1) Verify you’re actually hitting the OpenClaw relay on that port

Open this in your browser (or paste the output):

http://127.0.0.1:18792/extension/status

Expected JSON is something like:

{"connected":false}

• If you get 404 or it doesn’t load, the extension is pointing at the wrong thing / relay isn’t running on that port.

---

2) The token the extension wants (current behavior) is the HMAC-derived relay token

Your Node snippet is almost right, but the common failure on Windows is quoting/template-string issues.

Use this exact PowerShell + node one-liner (no template strings):

$env:PORT="18792"
$env:GW_TOKEN="PASTE_YOUR_gateway.auth.token_HERE"
node -e "const crypto=require('crypto'); const gw=(process.env.GW_TOKEN||'').trim(); const port=(process.env.PORT||'').trim(); console.log(crypto.createHmac('sha256', gw).update('openclaw-extension-relay-v1:' + port).digest('hex'));"

Take the hex output and paste THAT into the extension Options “Gateway token” field.

Important gotchas:

• Don’t include quotes/parentheses in the token.
• If you changed the port, you must re-derive (the port is part of the HMAC input).

---

3) If it still says “browser relay not running” when you click the extension icon