openclaw - 💡(How to fix) Fix [Bug]: Browser runtime ignores root browser.executablePath on 2026.4.26 [3 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73617Fetched 2026-04-29 06:17:23
View on GitHub
Comments
3
Participants
4
Timeline
6
Reactions
0
Author
Timeline (top)
commented ×3labeled ×2closed ×1

OpenClaw’s browser status/start path is not honoring the configured browser.executablePath even though /usr/bin/google-chrome exists and CDP is reachable on port 18800.

Error Message

Observed result: openclaw config get browser --json shows executablePath: "/usr/bin/google-chrome", but openclaw browser status still reports browser: unknown, detectedBrowser: unknown, detectedPath: auto, and openclaw browser start fails with GatewayClientRequestError: INVALID_REQUEST: Error: Error: No supported browser found; additionally, /usr/bin/google-chrome --version returns Google Chrome 147.0.7727.116 and curl http://127.0.0.1:18800/json/version returns Chrome CDP metadata.

Root Cause

🦞 OpenClaw 2026.4.26 (be8c246) One CLI to rule them all, and one more restart because you changed the port.

Code Example

openclaw config set browser.executablePath /usr/bin/google-chrome
openclaw config set browser.headless true
openclaw config set browser.noSandbox true
openclaw gateway restart
openclaw browser status
openclaw browser start

---

civil@debian:~/.openclaw$ openclaw config file
openclaw config get browser --json
openclaw config get browser.profiles.openclaw --json
openclaw gateway status

🦞 OpenClaw 2026.4.26 (be8c246)
   One CLI to rule them all, and one more restart because you changed the port.

~/.openclaw/openclaw.json
{
  "enabled": true,
  "executablePath": "/usr/bin/google-chrome",
  "headless": true,
  "noSandbox": true
}
Config path not found: browser.profiles.openclaw

🦞 OpenClaw 2026.4.26 (be8c246)
   I'm not saying your workflow is chaotic... I'm just bringing a linter and a helmet.


Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-29.log
Command: /usr/bin/node /home/civil/.local/share/pnpm/global/5/.pnpm/openclaw@2026.4.26/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

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

Gateway: bind=lan (0.0.0.0), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://192.168.0.96:18789/
Probe note: bind=lan listens on 0.0.0.0 (all interfaces); probing via 127.0.0.1.

Runtime: running (pid 178221, state active, sub running, last exit 0, reason 0)
Connectivity probe: ok
Capability: admin-capable

Listening: *:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting
civil@debian:~/.openclaw$ openclaw browser --json --browser-profile openclaw doctor --deep
openclaw browser --json --browser-profile openclaw status

/usr/bin/google-chrome --version
curl -s http://127.0.0.1:18800/json/version
OK gateway: browser control endpoint reachable
OK plugin: enabled
OK profile: openclaw (cdp)
FAIL browser: not running; run `openclaw browser start`
OK profiles: 2 configured
profile: openclaw
enabled: true
running: false
transport: cdp
cdpPort: 18800
cdpUrl: http://127.0.0.1:18800
browser: unknown
detectedBrowser: unknown
detectedPath: auto
headless: true (linux-display-fallback)
profileColor: #FF4500
Google Chrome 147.0.7727.116 
{
   "Browser": "Chrome/147.0.7727.116",
   "Protocol-Version": "1.3",
   "User-Agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/147.0.0.0 Safari/537.36",
   "V8-Version": "14.7.173.20",
   "WebKit-Version": "537.36 (@dbcf1b1bfb506cc580859bcb5ff9460a8443af90)",
   "webSocketDebuggerUrl": "ws://127.0.0.1:18800/devtools/browser/0497dbae-5bcb-46f5-a7ad-f3f7f42af7e1"
}
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

OpenClaw’s browser status/start path is not honoring the configured browser.executablePath even though /usr/bin/google-chrome exists and CDP is reachable on port 18800.

Steps to reproduce

openclaw config set browser.executablePath /usr/bin/google-chrome
openclaw config set browser.headless true
openclaw config set browser.noSandbox true
openclaw gateway restart
openclaw browser status
openclaw browser start

Observed result: status still shows detectedPath: auto, and start fails with No supported browser found.

Expected behavior

Per the browser docs, browser.executablePath should override auto-detection, so openclaw browser status should report /usr/bin/google-chrome instead of detectedPath: auto, and openclaw browser start should use that binary rather than failing with No supported browser found.

Actual behavior

Observed result: openclaw config get browser --json shows executablePath: "/usr/bin/google-chrome", but openclaw browser status still reports browser: unknown, detectedBrowser: unknown, detectedPath: auto, and openclaw browser start fails with GatewayClientRequestError: INVALID_REQUEST: Error: Error: No supported browser found; additionally, /usr/bin/google-chrome --version returns Google Chrome 147.0.7727.116 and curl http://127.0.0.1:18800/json/version returns Chrome CDP metadata.

OpenClaw version

2026.4.26

Operating system

Debian GNU/Linux 13 (trixie) x86_64

Install method

pnpm global

Model

ollama/glm-5.1:cloud

Provider / routing chain

OpenClaw -> Ollama Cloud -> GLM-5.1

Additional provider/model setup details

No response

Logs, screenshots, and evidence

civil@debian:~/.openclaw$ openclaw config file
openclaw config get browser --json
openclaw config get browser.profiles.openclaw --json
openclaw gateway status

🦞 OpenClaw 2026.4.26 (be8c246)
   One CLI to rule them all, and one more restart because you changed the port.

~/.openclaw/openclaw.json
{
  "enabled": true,
  "executablePath": "/usr/bin/google-chrome",
  "headless": true,
  "noSandbox": true
}
Config path not found: browser.profiles.openclaw

🦞 OpenClaw 2026.4.26 (be8c246)
   I'm not saying your workflow is chaotic... I'm just bringing a linter and a helmet.

Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-29.log
Command: /usr/bin/node /home/civil/.local/share/pnpm/global/5/.pnpm/[email protected]/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

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

Gateway: bind=lan (0.0.0.0), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://192.168.0.96:18789/
Probe note: bind=lan listens on 0.0.0.0 (all interfaces); probing via 127.0.0.1.

Runtime: running (pid 178221, state active, sub running, last exit 0, reason 0)
Connectivity probe: ok
Capability: admin-capable

Listening: *:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting
civil@debian:~/.openclaw$ openclaw browser --json --browser-profile openclaw doctor --deep
openclaw browser --json --browser-profile openclaw status

/usr/bin/google-chrome --version
curl -s http://127.0.0.1:18800/json/version
OK gateway: browser control endpoint reachable
OK plugin: enabled
OK profile: openclaw (cdp)
FAIL browser: not running; run `openclaw browser start`
OK profiles: 2 configured
profile: openclaw
enabled: true
running: false
transport: cdp
cdpPort: 18800
cdpUrl: http://127.0.0.1:18800
browser: unknown
detectedBrowser: unknown
detectedPath: auto
headless: true (linux-display-fallback)
profileColor: #FF4500
Google Chrome 147.0.7727.116 
{
   "Browser": "Chrome/147.0.7727.116",
   "Protocol-Version": "1.3",
   "User-Agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/147.0.0.0 Safari/537.36",
   "V8-Version": "14.7.173.20",
   "WebKit-Version": "537.36 (@dbcf1b1bfb506cc580859bcb5ff9460a8443af90)",
   "webSocketDebuggerUrl": "ws://127.0.0.1:18800/devtools/browser/0497dbae-5bcb-46f5-a7ad-f3f7f42af7e1"
}

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be resolved by verifying the browser.executablePath configuration and ensuring that the Google Chrome browser is properly installed and accessible at the specified path.

Guidance

  • Verify that the browser.executablePath is correctly set to /usr/bin/google-chrome by running openclaw config get browser --json and checking the output.
  • Check if the Google Chrome browser is installed and executable at the specified path by running /usr/bin/google-chrome --version.
  • Ensure that the Chrome CDP is reachable on port 18800 by running curl http://127.0.0.1:18800/json/version.
  • Try restarting the OpenClaw gateway and browser after updating the configuration to ensure the changes take effect.

Example

No code snippet is provided as the issue seems to be related to configuration and environment setup.

Notes

The issue might be related to the fact that openclaw browser status reports detectedPath: auto despite the browser.executablePath being set. This could indicate a problem with the auto-detection mechanism or the configuration not being applied correctly.

Recommendation

Apply the workaround by verifying the browser.executablePath configuration and ensuring that the Google Chrome browser is properly installed and accessible at the specified path. This should resolve the issue and allow the OpenClaw browser to start correctly.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Per the browser docs, browser.executablePath should override auto-detection, so openclaw browser status should report /usr/bin/google-chrome instead of detectedPath: auto, and openclaw browser start should use that binary rather than failing with No supported browser found.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING