Skip to content

[Bug]: Browser tool can’t reach browser control service under WSL2 (Chrome relay + extension set up) #30196

New issue
New issue
Closed
#30232
Closed
[Bug]: Browser tool can’t reach browser control service under WSL2 (Chrome relay + extension set up)#30196
#30232
Labels
bugSomething isn't working
@haquefamilyai-gif

Description

@haquefamilyai-gif
haquefamilyai-gif
opened on Mar 1, 2026

Summary

Environment

  • Host OS: Windows 11
  • WSL: Ubuntu on WSL2
    • Kernel: linux 6.6.87.2-microsoft-standard-WSL2 (x64)
  • Node: v22.22.0
  • OpenClaw:
    • Channel: stable (default)
    • Version: 2026.2.25 (doctor says “not git checkout”)
  • Install method: global package manager (likely npm -g or pnpm -g)
  • Gateway:
    • Bind: loopback (127.0.0.1)
    • Port: 18789
    • Status: reachable / OK
  • Browser:
    • google-chrome-stable running via WSLg
    • OpenClaw Browser Relay extension installed in WSL Chrome (not Windows Chrome)

What I’m trying to do

Use the browser tool from OpenClaw to control Chrome (via the OpenClaw Browser Relay extension) so the agent can log
in to websites (e.g., SpotOn) and run reports.

What I did

  1. Verified gateway is running in WSL:
  openclaw status

Key output:

  Dashboard       http://127.0.0.1:18789/
  OS              linux 6.6.87.2-microsoft-standard-WSL2 (x64) · node 22.22.0
  Gateway         local · ws://127.0.0.1:18789 (local loopback) · reachable
  Gateway service systemd installed · enabled · running (state active)
  1. Started Chrome from WSL:
  google-chrome-stable &
 - Chrome window opens on Windows via WSLg.
  1. In this WSL Chrome:
    • Installed OpenClaw Browser Relay from the Chrome Web Store.
    • Confirmed it appears under chrome://extensions.
    • Opened a normal tab (https://google.com).
    • Clicked the OpenClaw extension icon on that tab.
  2. Extension popup shows:
  OpenClaw Browser Relay - Powered By PAIO

  Click the toolbar button on a tab to attach / detach.

  Getting started
  If you see a red ! badge on the extension icon, the relay server is not reachable.
  Start OpenClaw's browser relay on this machine (Gateway or OpenClaw browser serve), then click the toolbar button
again.

  Relay port
  Port 18792
  Save
  Default: 18792. Extension connects to: http://127.0.0.1:18792/.
  Only change this if your OpenClaw profile uses a different cdpUrl port.

  Relay reachable at http://127.0.0.1:18792/

 - At this point, the extension itself looks configured and “no access needed”; earlier it showed a red badge, now

it’s in the “configured” state.
5. From the agent, trying to use the browser tool, e.g.:
- browser status or browser start (profile chrome)

What happens (actual behavior)

The OpenClaw browser tool consistently returns:

  Can't reach the OpenClaw browser control service. Restart the OpenClaw gateway (OpenClaw.app menubar, or `openclaw
gateway`). Do NOT retry the browser tool — it will keep failing. Use an alternative approach or inform the user that
the browser is currently unavailable. (Error: Error: Chrome extension relay is running, but no tab is connected. Click
the OpenClaw Chrome extension icon on a tab to attach it (profile "chrome").)

Even after:

  • Restarting the gateway: 
      openclaw gateway restart
  openclaw status --deep
  • Confirming Chrome is running from WSL with the extension installed.
  • Clicking the extension on a normal page tab.

The browser tool’s error message is now stale: the extension is installed and clicked on a normal tab, but the tool
continues to insist there is “no tab connected” and “Can’t reach the browser control service”.

Logs / console noise

From WSL Chrome, when browsing (likely unrelated, but including for completeness):

  [2965:2965:0228/200945.655510:ERROR:dbus/object_proxy.cc:572] Failed to call method:
org.freedesktop.DBus.Properties. GetAll: object_path= /org/freedesktop/UPower/devices/DisplayDevice:
org.freedesktop.DBus.Error.Servi ceUnknown: The name org.freedesktop.UPower was not provided by any .service files
  Created TensorFlow Lite XNNPACK delegate for CPU.
  [2965:2990:0228/200947.919087:ERROR:google_apis/gcm/engine/registration_request.cc:290] Registration response error
message: DEPRECATED_ENDPOINT
  [2965:2990:0228/201010.344670:ERROR:google_apis/gcm/engine/registration_request.cc:290] Registration response error
message: DEPRECATED_ENDPOINT

openclaw doctor also prints:

  This install is not a git checkout.
  Run `openclaw update` to update via your package manager (npm/pnpm), then rerun doctor.

Updating via openclaw update was skipped with:

  Update Result: SKIPPED
  Reason: not-git-install
  Skipped: this OpenClaw install isn't a git checkout, and the package manager couldn't be detected. Update via your
package manager.

What I expected

  • browser start / browser status to detect the WSL Chrome instance and the relay extension, and allow the agent to
    drive a tab (e.g. open URLs, click, type).
  • If there’s a misconfig between gateway and browser relay, a clearer diagnostic (“browser control service failed to
    start / port conflict / etc.”) rather than a repeated “no tab is connected” message when a tab has actually been
    clicked.

Impact

  • Browser automation is effectively unavailable on this setup (WSL2 + WSLg Chrome), even though:
    • Gateway is healthy (openclaw status OK).
    • WSL Chrome is running with the OpenClaw extension installed.
    • Extension is configured to http://127.0.0.1:18792.

Questions / Requests

  1. Is this a known limitation/bug with WSL2 + WSLg and the browser tool?
  2. Is there a recommended way to:
    • Explicitly start the browser control service, or
    • Adjust cdpUrl/ports/profile so the browser tool can reach it?
  3. Any extra diagnostics I can run (e.g., openclaw logs --follow, specific env vars) to help track why cdpReady is
    false and the tool thinks no tab is attached?

Thanks in advance—happy to run additional commands and share more logs if needed.

Steps to reproduce

Environment

  • Host OS: Windows 11
  • WSL: Ubuntu on WSL2
    • Kernel: linux 6.6.87.2-microsoft-standard-WSL2 (x64)
  • Node: v22.22.0
  • OpenClaw:
    • Channel: stable (default)
    • Version: 2026.2.25 (doctor says “not git checkout”)
  • Install method: global package manager (likely npm -g or pnpm -g)
  • Gateway:
    • Bind: loopback (127.0.0.1)
    • Port: 18789
    • Status: reachable / OK
  • Browser:
    • google-chrome-stable running via WSLg
    • OpenClaw Browser Relay extension installed in WSL Chrome (not Windows Chrome)

What I’m trying to do

Use the browser tool from OpenClaw to control Chrome (via the OpenClaw Browser Relay extension) so the agent can log
in to websites (e.g., SpotOn) and run reports.

What I did

  1. Verified gateway is running in WSL:
  openclaw status

Key output:

  Dashboard       http://127.0.0.1:18789/
  OS              linux 6.6.87.2-microsoft-standard-WSL2 (x64) · node 22.22.0
  Gateway         local · ws://127.0.0.1:18789 (local loopback) · reachable
  Gateway service systemd installed · enabled · running (state active)
  1. Started Chrome from WSL:
  google-chrome-stable &
 - Chrome window opens on Windows via WSLg.
  1. In this WSL Chrome:
    • Installed OpenClaw Browser Relay from the Chrome Web Store.
    • Confirmed it appears under chrome://extensions.
    • Opened a normal tab (https://google.com).
    • Clicked the OpenClaw extension icon on that tab.
  2. Extension popup shows:
  OpenClaw Browser Relay - Powered By PAIO

  Click the toolbar button on a tab to attach / detach.

  Getting started
  If you see a red ! badge on the extension icon, the relay server is not reachable.
  Start OpenClaw's browser relay on this machine (Gateway or OpenClaw browser serve), then click the toolbar button
again.

  Relay port
  Port 18792
  Save
  Default: 18792. Extension connects to: http://127.0.0.1:18792/.
  Only change this if your OpenClaw profile uses a different cdpUrl port.

  Relay reachable at http://127.0.0.1:18792/

 - At this point, the extension itself looks configured and “no access needed”; earlier it showed a red badge, now

it’s in the “configured” state.
5. From the agent, trying to use the browser tool, e.g.:
- browser status or browser start (profile chrome)

What happens (actual behavior)

The OpenClaw browser tool consistently returns:

  Can't reach the OpenClaw browser control service. Restart the OpenClaw gateway (OpenClaw.app menubar, or `openclaw
gateway`). Do NOT retry the browser tool — it will keep failing. Use an alternative approach or inform the user that
the browser is currently unavailable. (Error: Error: Chrome extension relay is running, but no tab is connected. Click
the OpenClaw Chrome extension icon on a tab to attach it (profile "chrome").)

Even after:

  • Restarting the gateway: 
      openclaw gateway restart
  openclaw status --deep
  • Confirming Chrome is running from WSL with the extension installed.
  • Clicking the extension on a normal page tab.

The browser tool’s error message is now stale: the extension is installed and clicked on a normal tab, but the tool
continues to insist there is “no tab connected” and “Can’t reach the browser control service”.

Logs / console noise

From WSL Chrome, when browsing (likely unrelated, but including for completeness):

  [2965:2965:0228/200945.655510:ERROR:dbus/object_proxy.cc:572] Failed to call method:
org.freedesktop.DBus.Properties. GetAll: object_path= /org/freedesktop/UPower/devices/DisplayDevice:
org.freedesktop.DBus.Error.Servi ceUnknown: The name org.freedesktop.UPower was not provided by any .service files
  Created TensorFlow Lite XNNPACK delegate for CPU.
  [2965:2990:0228/200947.919087:ERROR:google_apis/gcm/engine/registration_request.cc:290] Registration response error
message: DEPRECATED_ENDPOINT
  [2965:2990:0228/201010.344670:ERROR:google_apis/gcm/engine/registration_request.cc:290] Registration response error
message: DEPRECATED_ENDPOINT

openclaw doctor also prints:

  This install is not a git checkout.
  Run `openclaw update` to update via your package manager (npm/pnpm), then rerun doctor.

Updating via openclaw update was skipped with:

  Update Result: SKIPPED
  Reason: not-git-install
  Skipped: this OpenClaw install isn't a git checkout, and the package manager couldn't be detected. Update via your
package manager.

What I expected

  • browser start / browser status to detect the WSL Chrome instance and the relay extension, and allow the agent to
    drive a tab (e.g. open URLs, click, type).
  • If there’s a misconfig between gateway and browser relay, a clearer diagnostic (“browser control service failed to
    start / port conflict / etc.”) rather than a repeated “no tab is connected” message when a tab has actually been
    clicked.

Impact

  • Browser automation is effectively unavailable on this setup (WSL2 + WSLg Chrome), even though:
    • Gateway is healthy (openclaw status OK).
    • WSL Chrome is running with the OpenClaw extension installed.
    • Extension is configured to http://127.0.0.1:18792.

Questions / Requests

  1. Is this a known limitation/bug with WSL2 + WSLg and the browser tool?
  2. Is there a recommended way to:
    • Explicitly start the browser control service, or
    • Adjust cdpUrl/ports/profile so the browser tool can reach it?
  3. Any extra diagnostics I can run (e.g., openclaw logs --follow, specific env vars) to help track why cdpReady is
    false and the tool thinks no tab is attached?

Thanks in advance—happy to run additional commands and share more logs if needed.

Expected behavior

Environment

  • Host OS: Windows 11
  • WSL: Ubuntu on WSL2
    • Kernel: linux 6.6.87.2-microsoft-standard-WSL2 (x64)
  • Node: v22.22.0
  • OpenClaw:
    • Channel: stable (default)
    • Version: 2026.2.25 (doctor says “not git checkout”)
  • Install method: global package manager (likely npm -g or pnpm -g)
  • Gateway:
    • Bind: loopback (127.0.0.1)
    • Port: 18789
    • Status: reachable / OK
  • Browser:
    • google-chrome-stable running via WSLg
    • OpenClaw Browser Relay extension installed in WSL Chrome (not Windows Chrome)

What I’m trying to do

Use the browser tool from OpenClaw to control Chrome (via the OpenClaw Browser Relay extension) so the agent can log
in to websites (e.g., SpotOn) and run reports.

What I did

  1. Verified gateway is running in WSL:
  openclaw status

Key output:

  Dashboard       http://127.0.0.1:18789/
  OS              linux 6.6.87.2-microsoft-standard-WSL2 (x64) · node 22.22.0
  Gateway         local · ws://127.0.0.1:18789 (local loopback) · reachable
  Gateway service systemd installed · enabled · running (state active)
  1. Started Chrome from WSL:
  google-chrome-stable &
 - Chrome window opens on Windows via WSLg.
  1. In this WSL Chrome:
    • Installed OpenClaw Browser Relay from the Chrome Web Store.
    • Confirmed it appears under chrome://extensions.
    • Opened a normal tab (https://google.com).
    • Clicked the OpenClaw extension icon on that tab.
  2. Extension popup shows:
  OpenClaw Browser Relay - Powered By PAIO

  Click the toolbar button on a tab to attach / detach.

  Getting started
  If you see a red ! badge on the extension icon, the relay server is not reachable.
  Start OpenClaw's browser relay on this machine (Gateway or OpenClaw browser serve), then click the toolbar button
again.

  Relay port
  Port 18792
  Save
  Default: 18792. Extension connects to: http://127.0.0.1:18792/.
  Only change this if your OpenClaw profile uses a different cdpUrl port.

  Relay reachable at http://127.0.0.1:18792/

 - At this point, the extension itself looks configured and “no access needed”; earlier it showed a red badge, now

it’s in the “configured” state.
5. From the agent, trying to use the browser tool, e.g.:
- browser status or browser start (profile chrome)

What happens (actual behavior)

The OpenClaw browser tool consistently returns:

  Can't reach the OpenClaw browser control service. Restart the OpenClaw gateway (OpenClaw.app menubar, or `openclaw
gateway`). Do NOT retry the browser tool — it will keep failing. Use an alternative approach or inform the user that
the browser is currently unavailable. (Error: Error: Chrome extension relay is running, but no tab is connected. Click
the OpenClaw Chrome extension icon on a tab to attach it (profile "chrome").)

Even after:

  • Restarting the gateway: 
      openclaw gateway restart
  openclaw status --deep
  • Confirming Chrome is running from WSL with the extension installed.
  • Clicking the extension on a normal page tab.

The browser tool’s error message is now stale: the extension is installed and clicked on a normal tab, but the tool
continues to insist there is “no tab connected” and “Can’t reach the browser control service”.

Logs / console noise

From WSL Chrome, when browsing (likely unrelated, but including for completeness):

  [2965:2965:0228/200945.655510:ERROR:dbus/object_proxy.cc:572] Failed to call method:
org.freedesktop.DBus.Properties. GetAll: object_path= /org/freedesktop/UPower/devices/DisplayDevice:
org.freedesktop.DBus.Error.Servi ceUnknown: The name org.freedesktop.UPower was not provided by any .service files
  Created TensorFlow Lite XNNPACK delegate for CPU.
  [2965:2990:0228/200947.919087:ERROR:google_apis/gcm/engine/registration_request.cc:290] Registration response error
message: DEPRECATED_ENDPOINT
  [2965:2990:0228/201010.344670:ERROR:google_apis/gcm/engine/registration_request.cc:290] Registration response error
message: DEPRECATED_ENDPOINT

openclaw doctor also prints:

  This install is not a git checkout.
  Run `openclaw update` to update via your package manager (npm/pnpm), then rerun doctor.

Updating via openclaw update was skipped with:

  Update Result: SKIPPED
  Reason: not-git-install
  Skipped: this OpenClaw install isn't a git checkout, and the package manager couldn't be detected. Update via your
package manager.

What I expected

  • browser start / browser status to detect the WSL Chrome instance and the relay extension, and allow the agent to
    drive a tab (e.g. open URLs, click, type).
  • If there’s a misconfig between gateway and browser relay, a clearer diagnostic (“browser control service failed to
    start / port conflict / etc.”) rather than a repeated “no tab is connected” message when a tab has actually been
    clicked.

Impact

  • Browser automation is effectively unavailable on this setup (WSL2 + WSLg Chrome), even though:
    • Gateway is healthy (openclaw status OK).
    • WSL Chrome is running with the OpenClaw extension installed.
    • Extension is configured to http://127.0.0.1:18792.

Questions / Requests

  1. Is this a known limitation/bug with WSL2 + WSLg and the browser tool?
  2. Is there a recommended way to:
    • Explicitly start the browser control service, or
    • Adjust cdpUrl/ports/profile so the browser tool can reach it?
  3. Any extra diagnostics I can run (e.g., openclaw logs --follow, specific env vars) to help track why cdpReady is
    false and the tool thinks no tab is attached?

Thanks in advance—happy to run additional commands and share more logs if needed.

Actual behavior

Environment

  • Host OS: Windows 11
  • WSL: Ubuntu on WSL2
    • Kernel: linux 6.6.87.2-microsoft-standard-WSL2 (x64)
  • Node: v22.22.0
  • OpenClaw:
    • Channel: stable (default)
    • Version: 2026.2.25 (doctor says “not git checkout”)
  • Install method: global package manager (likely npm -g or pnpm -g)
  • Gateway:
    • Bind: loopback (127.0.0.1)
    • Port: 18789
    • Status: reachable / OK
  • Browser:
    • google-chrome-stable running via WSLg
    • OpenClaw Browser Relay extension installed in WSL Chrome (not Windows Chrome)

What I’m trying to do

Use the browser tool from OpenClaw to control Chrome (via the OpenClaw Browser Relay extension) so the agent can log
in to websites (e.g., SpotOn) and run reports.

What I did

  1. Verified gateway is running in WSL:
  openclaw status

Key output:

  Dashboard       http://127.0.0.1:18789/
  OS              linux 6.6.87.2-microsoft-standard-WSL2 (x64) · node 22.22.0
  Gateway         local · ws://127.0.0.1:18789 (local loopback) · reachable
  Gateway service systemd installed · enabled · running (state active)
  1. Started Chrome from WSL:
  google-chrome-stable &
 - Chrome window opens on Windows via WSLg.
  1. In this WSL Chrome:
    • Installed OpenClaw Browser Relay from the Chrome Web Store.
    • Confirmed it appears under chrome://extensions.
    • Opened a normal tab (https://google.com).
    • Clicked the OpenClaw extension icon on that tab.
  2. Extension popup shows:
  OpenClaw Browser Relay - Powered By PAIO

  Click the toolbar button on a tab to attach / detach.

  Getting started
  If you see a red ! badge on the extension icon, the relay server is not reachable.
  Start OpenClaw's browser relay on this machine (Gateway or OpenClaw browser serve), then click the toolbar button
again.

  Relay port
  Port 18792
  Save
  Default: 18792. Extension connects to: http://127.0.0.1:18792/.
  Only change this if your OpenClaw profile uses a different cdpUrl port.

  Relay reachable at http://127.0.0.1:18792/

 - At this point, the extension itself looks configured and “no access needed”; earlier it showed a red badge, now

it’s in the “configured” state.
5. From the agent, trying to use the browser tool, e.g.:
- browser status or browser start (profile chrome)

What happens (actual behavior)

The OpenClaw browser tool consistently returns:

  Can't reach the OpenClaw browser control service. Restart the OpenClaw gateway (OpenClaw.app menubar, or `openclaw
gateway`). Do NOT retry the browser tool — it will keep failing. Use an alternative approach or inform the user that
the browser is currently unavailable. (Error: Error: Chrome extension relay is running, but no tab is connected. Click
the OpenClaw Chrome extension icon on a tab to attach it (profile "chrome").)

Even after:

  • Restarting the gateway: 
      openclaw gateway restart
  openclaw status --deep
  • Confirming Chrome is running from WSL with the extension installed.
  • Clicking the extension on a normal page tab.

The browser tool’s error message is now stale: the extension is installed and clicked on a normal tab, but the tool
continues to insist there is “no tab connected” and “Can’t reach the browser control service”.

Logs / console noise

From WSL Chrome, when browsing (likely unrelated, but including for completeness):

  [2965:2965:0228/200945.655510:ERROR:dbus/object_proxy.cc:572] Failed to call method:
org.freedesktop.DBus.Properties. GetAll: object_path= /org/freedesktop/UPower/devices/DisplayDevice:
org.freedesktop.DBus.Error.Servi ceUnknown: The name org.freedesktop.UPower was not provided by any .service files
  Created TensorFlow Lite XNNPACK delegate for CPU.
  [2965:2990:0228/200947.919087:ERROR:google_apis/gcm/engine/registration_request.cc:290] Registration response error
message: DEPRECATED_ENDPOINT
  [2965:2990:0228/201010.344670:ERROR:google_apis/gcm/engine/registration_request.cc:290] Registration response error
message: DEPRECATED_ENDPOINT

openclaw doctor also prints:

  This install is not a git checkout.
  Run `openclaw update` to update via your package manager (npm/pnpm), then rerun doctor.

Updating via openclaw update was skipped with:

  Update Result: SKIPPED
  Reason: not-git-install
  Skipped: this OpenClaw install isn't a git checkout, and the package manager couldn't be detected. Update via your
package manager.

What I expected

  • browser start / browser status to detect the WSL Chrome instance and the relay extension, and allow the agent to
    drive a tab (e.g. open URLs, click, type).
  • If there’s a misconfig between gateway and browser relay, a clearer diagnostic (“browser control service failed to
    start / port conflict / etc.”) rather than a repeated “no tab is connected” message when a tab has actually been
    clicked.

Impact

  • Browser automation is effectively unavailable on this setup (WSL2 + WSLg Chrome), even though:
    • Gateway is healthy (openclaw status OK).
    • WSL Chrome is running with the OpenClaw extension installed.
    • Extension is configured to http://127.0.0.1:18792.

Questions / Requests

  1. Is this a known limitation/bug with WSL2 + WSLg and the browser tool?
  2. Is there a recommended way to:
    • Explicitly start the browser control service, or
    • Adjust cdpUrl/ports/profile so the browser tool can reach it?
  3. Any extra diagnostics I can run (e.g., openclaw logs --follow, specific env vars) to help track why cdpReady is
    false and the tool thinks no tab is attached?

Thanks in advance—happy to run additional commands and share more logs if needed.

OpenClaw version

Version: 2026.2.25

Operating system

Windows 11

Install method

No response

Logs, screenshots, and evidence

Environment

 - Host OS: Windows 11
 - WSL: Ubuntu on WSL2
     - Kernel: linux 6.6.87.2-microsoft-standard-WSL2 (x64)
 - Node: v22.22.0
 - OpenClaw:
     - Channel: stable (default)
     - Version: 2026.2.25 (doctor says “not git checkout”)
 - Install method: global package manager (likely npm -g or pnpm -g)
 - Gateway:
     - Bind: loopback (127.0.0.1)
     - Port: 18789
     - Status: reachable / OK
 - Browser:
     - google-chrome-stable running via WSLg
     - OpenClaw Browser Relay extension installed in WSL Chrome (not Windows Chrome)

 What I’m trying to do

 Use the browser tool from OpenClaw to control Chrome (via the OpenClaw Browser Relay extension) so the agent can log
 in to websites (e.g., SpotOn) and run reports.

 What I did

 1. Verified gateway is running in WSL:
   
     openclaw status
   
   Key output:
   
     Dashboard       http://127.0.0.1:18789/
     OS              linux 6.6.87.2-microsoft-standard-WSL2 (x64) · node 22.22.0
     Gateway         local · ws://127.0.0.1:18789 (local loopback) · reachable
     Gateway service systemd installed · enabled · running (state active)
   
 2. Started Chrome from WSL:
   
     google-chrome-stable &
   
     - Chrome window opens on Windows via WSLg.
 3. In this WSL Chrome:
     - Installed OpenClaw Browser Relay from the Chrome Web Store.
     - Confirmed it appears under chrome://extensions.
     - Opened a normal tab (https://google.com).
     - Clicked the OpenClaw extension icon on that tab.
 4. Extension popup shows:
   
     OpenClaw Browser Relay - Powered By PAIO

     Click the toolbar button on a tab to attach / detach.

     Getting started
     If you see a red ! badge on the extension icon, the relay server is not reachable.
     Start OpenClaw's browser relay on this machine (Gateway or OpenClaw browser serve), then click the toolbar button
 again.

     Relay port
     Port 18792
     Save
     Default: 18792. Extension connects to: http://127.0.0.1:18792/.
     Only change this if your OpenClaw profile uses a different cdpUrl port.

     Relay reachable at http://127.0.0.1:18792/
   
     - At this point, the extension itself looks configured and “no access needed”; earlier it showed a red badge, now
 it’s in the “configured” state.
 5. From the agent, trying to use the browser tool, e.g.:
     - browser status or browser start (profile chrome)

 What happens (actual behavior)

 The OpenClaw browser tool consistently returns:

 
   Can't reach the OpenClaw browser control service. Restart the OpenClaw gateway (OpenClaw.app menubar, or `openclaw
 gateway`). Do NOT retry the browser tool — it will keep failing. Use an alternative approach or inform the user that
 the browser is currently unavailable. (Error: Error: Chrome extension relay is running, but no tab is connected. Click
 the OpenClaw Chrome extension icon on a tab to attach it (profile "chrome").)
 

 Even after:

 - Restarting the gateway:
   
     openclaw gateway restart
     openclaw status --deep
   
 - Confirming Chrome is running from WSL with the extension installed.
 - Clicking the extension on a normal page tab.

 The browser tool’s error message is now stale: the extension is installed and clicked on a normal tab, but the tool
 continues to insist there is “no tab connected” and “Can’t reach the browser control service”.

 Logs / console noise

 From WSL Chrome, when browsing (likely unrelated, but including for completeness):

 
   [2965:2965:0228/200945.655510:ERROR:dbus/object_proxy.cc:572] Failed to call method:
 org.freedesktop.DBus.Properties. GetAll: object_path= /org/freedesktop/UPower/devices/DisplayDevice:
 org.freedesktop.DBus.Error.Servi ceUnknown: The name org.freedesktop.UPower was not provided by any .service files
   Created TensorFlow Lite XNNPACK delegate for CPU.
   [2965:2990:0228/200947.919087:ERROR:google_apis/gcm/engine/registration_request.cc:290] Registration response error
 message: DEPRECATED_ENDPOINT
   [2965:2990:0228/201010.344670:ERROR:google_apis/gcm/engine/registration_request.cc:290] Registration response error
 message: DEPRECATED_ENDPOINT
 

 openclaw doctor also prints:

 
   This install is not a git checkout.
   Run `openclaw update` to update via your package manager (npm/pnpm), then rerun doctor.
 

 Updating via openclaw update was skipped with:

 
   Update Result: SKIPPED
   Reason: not-git-install
   Skipped: this OpenClaw install isn't a git checkout, and the package manager couldn't be detected. Update via your
 package manager.
 

 What I expected

 - browser start / browser status to detect the WSL Chrome instance and the relay extension, and allow the agent to
 drive a tab (e.g. open URLs, click, type).
 - If there’s a misconfig between gateway and browser relay, a clearer diagnostic (“browser control service failed to
 start / port conflict / etc.”) rather than a repeated “no tab is connected” message when a tab has actually been
 clicked.

 Impact

 - Browser automation is effectively unavailable on this setup (WSL2 + WSLg Chrome), even though:
     - Gateway is healthy (openclaw status OK).
     - WSL Chrome is running with the OpenClaw extension installed.
     - Extension is configured to http://127.0.0.1:18792.

 Questions / Requests

 1. Is this a known limitation/bug with WSL2 + WSLg and the browser tool?
 2. Is there a recommended way to:
     - Explicitly start the browser control service, or
     - Adjust cdpUrl/ports/profile so the browser tool can reach it?
 3. Any extra diagnostics I can run (e.g., openclaw logs --follow, specific env vars) to help track why cdpReady is
 false and the tool thinks no tab is attached?

 Thanks in advance—happy to run additional commands and share more logs if needed.

Impact and severity

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions