#dedicated chrome browser issues
1 messages · Page 1 of 1 (latest)
Yeah — if the openclaw-managed “orange” Chrome profile is being flaky on macOS, the most reliable workaround is usually: don’t use the dedicated browser at all → use the Chrome extension relay so OpenClaw drives your normal Chrome tab.
Option A (recommended): Chrome extension relay (use your existing Chrome)
Docs: https://docs.openclaw.ai/tools/chrome-extension
Quick steps:
openclaw browser extension installopenclaw browser extension path→ load that folder via Chrome →chrome://extensions→ Developer mode → “Load unpacked”- Pin the extension, open the tab you want controlled, click the extension icon (badge shows ON)
- Use browser profile
chrome(built-in):- CLI sanity check:
openclaw browser --browser-profile chrome tabs
- CLI sanity check:
This avoids a bunch of the dedicated-profile weirdness because it’s just attaching to a real tab.
Option B: Keep “dedicated” but try a different Chromium
OpenClaw can launch/control Chrome / Brave / Edge / Chromium (and you can override via browser.executablePath). Docs: https://docs.openclaw.ai/tools/browser
Sometimes Brave or Edge behaves better on a given Mac.