#OpenClaw - Openrouter

1 messages · Page 1 of 1 (latest)

frail tusk
#

I am using openrouter as the model and OpenClaw ai is not actioning anything. Browser relay is red badge. No such path exists.

I need help to setup OpenClaw so I can have it do YouTube automations. Create videos, upload to YouTube, after review.

glossy cobaltBOT
#

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

mortal stagBOT
#

A red ! badge + “No such path exists” usually means your Chrome extension relay isn’t actually set up on the machine where Chrome is running (common when the Gateway is on a VPS, but you’re trying to load an extension path that exists only on the VPS).

1) Fix the Browser Relay (red badge / bad path)

Follow the official doc: https://docs.openclaw.ai/tools/chrome-extension

Key points:

  • The extension files must live on the same computer as Chrome.
  • Don’t load it from node_modules. You must run:
openclaw browser extension install
openclaw browser extension path

Then in Chrome:
chrome://extensions → Developer mode → Load unpacked → select the folder from extension path.

#

In the extension Options, set:

  • Port: default is 18792
    • Doc note: Extension relay port = gateway.port + 3 (so if your Gateway port isn’t 18789, your relay port changes).
  • Gateway token: must match gateway.auth.token / OPENCLAW_GATEWAY_TOKEN

Badge meanings (from docs):

  • ON = attached and controllable
  • ! = relay not reachable or not authenticated (Gateway not running locally / wrong port / wrong token)

If your Gateway is remote (VPS): you typically need to run a node host on your local machine (the one with Chrome) so the Gateway can proxy browser control there:
https://docs.openclaw.ai/cli/node

2) “OpenRouter model isn’t actioning anything”

Before blaming OpenRouter: confirm the Gateway + tool policy are healthy. Please paste these outputs:

# 
openclaw --version
openclaw status --all
openclaw models status
openclaw gateway status

Common causes:

  • Tools not allowed by policy (so it can chat but won’t call browser/exec)
  • You’re in a sandboxed agent and host browser control is blocked (see the “Sandboxing” section in the chrome-extension doc)
  • The specific OpenRouter-routed model you picked is weak at tool-calling (to isolate this, try switching temporarily to a known tool-capable model just for debugging, then switch back)

OpenRouter setup doc (for config sanity): https://docs.openclaw.ai/providers/openrouter

3) YouTube automation expectation-setting (practical path)

  • Uploading + metadata + thumbnails: doable via browser automation (YouTube Studio) once the browser surface works.
  • “Create videos”: OpenClaw doesn’t magically generate full videos by itself; you’ll need a pipeline (scripts, ffmpeg, or a video-generation API) that OpenClaw orchestrates.
#
  • “After review”: easiest is to automate up to draft / unlisted, then require an approval step before “Publish”.

Reply with:

  1. Is your Gateway running locally or on a VPS?
  2. The outputs from the 4 commands above
  3. What port is your Gateway on (gateway.port), if not default 18789
frail tusk
#
  1. Gateway is running locally
  2. Install successful but path is not found
  3. Default port 18792
mortal stagBOT
#

If the Gateway is truly local on the same machine as Chrome, then:

  • Gateway port is usually 18789
  • Browser control service is 18791 (gateway + 2)
  • Extension relay is 18792 (gateway + 3)

So “default port 18792” is the relay port, not the gateway port.

Why you’re seeing “No such path exists”

That almost always happens when Chrome can’t see the folder you’re trying to “Load unpacked” from — typically because OpenClaw is running in a different filesystem context, e.g.:

  • OpenClaw running in WSL2 but Chrome is Windows Chrome
  • OpenClaw running in Docker but Chrome is on the host
  • OpenClaw running as a different user than the one you’re browsing with

In those cases, openclaw browser extension path prints a path that exists for OpenClaw, but does not exist for Chrome.

#

1) Quick check: are you in WSL / Docker?

What OS are you on, and are you running OpenClaw in WSL2 or Docker?

If yes: you generally need to either

  • run OpenClaw on the same OS environment as Chrome (Windows OpenClaw for Windows Chrome), or
  • copy the extension folder to a Windows-native path and ensure the relay port is reachable from Windows (this can get fiddly)

2) Please paste these command outputs (verbatim)

These will tell us exactly what’s going on:

openclaw --version
openclaw gateway status
openclaw config get gateway.port
openclaw browser extension install
openclaw browser extension path
#

3) Red ! badge (relay auth/reachability)

Per the docs, ! means the extension can’t reach/auth the relay. Once the path issue is fixed, also verify in the extension Options:

  • Port = 18792 (unless you changed gateway.port)
  • Gateway token matches:
    openclaw config get gateway.auth.token

Docs (worth following step-by-step):
https://docs.openclaw.ai/tools/chrome-extension

Once the extension loads and the badge can show ON on a tab (attached), tool actions should start working again — and then we can talk about the YouTube pipeline (draft upload + “approval gate” before publish).

frail tusk
#

PS C:\WINDOWS\system32> openclaw --version
2026.2.26
PS C:\WINDOWS\system32> openclaw gateway status

🦞 OpenClaw 2026.2.26 (bc50708) — Claws out, commit in—let's ship something mildly responsible.

|
o
Service: Scheduled Task (registered)
File logs: ~\AppData\Local\Temp\openclaw\openclaw-2026-03-01.log
Command: C:\Program Files\nodejs\node.exe C:\Users\AIBot\AppData\Roaming\npm\node_modules\openclaw\dist\index.js gateway --port 18789
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): ~.openclaw\openclaw.json
Config (service): ~.openclaw\openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: stopped (state Ready, last run time 2026-03-01 5:25:54 PM)
RPC probe: ok

Service is loaded but not running (likely exited immediately).
File logs: C:\Users\AIBot\AppData\Local\Temp\openclaw\openclaw-2026-03-01.log
Logs: schtasks /Query /TN "OpenClaw Gateway" /V /FO LIST

Listening: 127.0.0.1:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting
PS C:\WINDOWS\system32> openclaw config get gateway.port

🦞 OpenClaw 2026.2.26 (bc50708) — Turning "I'll reply later" into "my bot replied instantly".

18789

#

PS C:\WINDOWS\system32> openclaw browser extension install

🦞 OpenClaw 2026.2.26 (bc50708) — I'll do the boring stuff while you dramatically stare at the logs like it's cinema.

~.openclaw\browser\chrome-extension
Copied to clipboard.
Next:

  • Chrome → chrome://extensions → enable “Developer mode”
  • “Load unpacked” → select: ~.openclaw\browser\chrome-extension
  • Pin “OpenClaw Browser Relay”, then click it on the tab (badge shows ON)

Docs: docs.openclaw.ai/tools/chrome-extension
PS C:\WINDOWS\system32> openclaw browser extension path

🦞 OpenClaw 2026.2.26 (bc50708) — Shell yeah—I'm here to pinch the toil and leave you the glory.

~.openclaw\browser\chrome-extension
Copied to clipboard.
PS C:\WINDOWS\system32>

mortal stagBOT
#

Your openclaw gateway status output already explains most of this:

  • Runtime: stopped / “Service is loaded but not running (likely exited immediately)”
  • If the Gateway isn’t actually staying up, the extension relay on 127.0.0.1:18792 won’t be reachable, so the Chrome badge stays red ! and the agent won’t be able to drive the browser.

There’s also a confusing bit: it says RPC probe: ok and Listening: 127.0.0.1:18789 — that usually means you’ve got some gateway process responding, but the Scheduled Task gateway isn’t the one running (or it’s crashing and something else is still bound). Easiest is to get to a clean “gateway definitely running” state.

A) First: make sure the Gateway is actually running (and stays running)

Run:

openclaw gateway restart
openclaw gateway status
openclaw logs --follow

If it exits immediately again, openclaw logs --follow will show why (config parse error, missing file, permissions, etc.). Paste the error lines (don’t paste tokens).

#

Docs: https://docs.openclaw.ai/help/faq.md (see “First 60 seconds if something’s broken”)

B) Then: fix the “extension path not found” (this is the usual culprit)

On Windows, you should be able to do:

openclaw browser extension install
openclaw browser extension path

Take the path it prints and verify it exists:

$P = (openclaw browser extension path).Trim()
dir $P
explorer $P
#

Two super common mistakes:

  1. Chrome is running under a different Windows user than the one you installed OpenClaw as (your user here looks like C:\Users\AIBot\...). The extension folder must exist for the same user that’s loading it in Chrome.
  2. In Chrome “Load unpacked”, you selected the wrong level of folder — you need the folder that contains manifest.json.

Official guide: https://docs.openclaw.ai/tools/chrome-extension.md

C) Red ! badge: set port + token in extension Options

Once the extension is loaded, open the extension Options and set:

  • Port: 18792 (correct for gateway.port 18789; relay is gateway+3)
  • Gateway token: must match:
    openclaw config get gateway.auth.token
    If that’s empty, generate one:
# 
  openclaw doctor --generate-gateway-token
  openclaw gateway restart

After that, open a tab and click the extension icon so it shows ON (attached).

If you paste the output of these two commands, we can pinpoint the “no such path” part immediately:

openclaw browser extension install
openclaw browser extension path

(again: please don’t paste any tokens)

#

Nice — extension is installed; the problem is the path format.

~\.openclaw\browser\chrome-extension is a shell shorthand, but Chrome’s “Load unpacked” file picker does not understand ~, so it shows up as “no such path”.

Do this on Windows

  1. Open the real folder in Explorer:
explorer "$env:USERPROFILE\.openclaw\browser\chrome-extension"

  1. In that folder, confirm you see a manifest.json file.

  2. Chrome → chrome://extensions → Developer mode → Load unpacked → select:
    C:\Users\AIBot\.openclaw\browser\chrome-extension (the full path)

If the badge is still red !

#

That means the relay isn’t reachable/auth’d (most often because the Gateway isn’t actually running).

Your earlier openclaw gateway status showed Runtime: stopped (exited immediately), so fix that first:

openclaw gateway restart
openclaw gateway status
openclaw logs --follow

Then in the extension Options set:

  • Port: 18792 (correct for gateway.port 18789)
  • Gateway token: value from openclaw config get gateway.auth.token

If you still get stuck, paste:

  • the latest openclaw gateway status
  • the last ~30 lines from openclaw logs --follow right after restart (no tokens)
frail tusk
#

Found the gateway token, through the openclaw config.

mortal stagBOT
#

Good — that’s one of the two things the extension needs.

Now the checklist to get from “red !” → “badge ON”:

1) Load the extension using a real Windows path (not ~)

Chrome can’t load ~\.openclaw\....

Use:

explorer "$env:USERPROFILE\.openclaw\browser\chrome-extension"

Then Chrome → chrome://extensions → Developer mode → Load unpacked → select that folder (must contain manifest.json).

2) Set the token + port in the extension Options

Extension icon → Options:

#
  • Port: 18792 (since your gateway is on 18789)
  • Gateway token: paste the token you found

Save.

3) Make sure the Gateway is actually running

Earlier you had Runtime: stopped, which will always keep the badge red.

Run:

openclaw gateway restart
openclaw gateway status

You want it to say it’s running (not “stopped / exited immediately”).

#

If it still stops, run:

openclaw logs --follow

and paste the first error stack / message after the restart (tokens redacted).

4) Attach a tab (badge must show ON)

Open a normal Chrome tab (e.g. youtube.com), then click the extension icon once. It should flip to ON.

Once you have ON, OpenClaw can actually drive the browser, and we can move to the YouTube automation flow (draft upload + review gate + publish).