openclaw browser --browser-profile openclaw start | Friends of the Crustacean 🦞🤝 | Page 1

nova furnace Apr 17, 2026, 11:35 AM

#

openclaw browser --browser-profile openclaw start

🦞 OpenClaw 2026.4.15 (041266a) — I don't judge, but your missing API keys are absolutely judging you.

│
◇
GatewayClientRequestError: Error: browser.executablePath not found: /usr/bin/google-chrome-stable

I'm on macos

white lindenBOT Apr 17, 2026, 11:35 AM

#

pallid streamBOT Apr 17, 2026, 11:35 AM

#

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

white lindenBOT Apr 17, 2026, 11:35 AM

#

bitter violetBOT Apr 17, 2026, 11:37 AM

#

That error is just OpenClaw trying to use a Linux browser path on macOS:

/usr/bin/google-chrome-stable

So yeah, it won't exist there.

Try this first:

openclaw config get browser.executablePath
openclaw config unset browser.executablePath
openclaw gateway restart
openclaw browser --browser-profile openclaw start

On macOS, OpenClaw should auto-detect Chrome/Brave/Edge from /Applications.

#

If you want to pin Brave explicitly instead:

openclaw config set browser.executablePath "/Applications/Brave Browser.app/Contents/MacOS/Brave Browser"
openclaw gateway restart

If it still fails, paste these:

openclaw status
openclaw config get browser.executablePath

Docs: https://docs.openclaw.ai/tools/browser and https://docs.openclaw.ai/gateway/troubleshooting

If that fixes it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it.

nova furnace Apr 17, 2026, 11:41 AM

#

Relay not reachable/authenticated at http://127.0.0.1:18792/. Start OpenClaw browser relay and verify token.

bitter violetBOT Apr 17, 2026, 11:42 AM

#

Okay, that’s actually useful, it means you got past the bad macOS executable path.

This new error smells like stale legacy browser relay config.
http://127.0.0.1:18792 is the old extension/relay path, not the normal current openclaw managed-browser flow.

Try this next:

openclaw doctor --fix
openclaw gateway restart
openclaw browser profiles
openclaw browser --browser-profile openclaw start

A few relevant notes:

--browser-profile openclaw should not need an old relay token

#

current host-local attach uses Chrome MCP / existing-session, not the old extension relay
openclaw doctor --fix should migrate:
- browser.profiles.*.driver: "extension" → "existing-session"
- remove browser.relayBindHost

If it still mentions 18792, paste these:

openclaw config get browser
openclaw status --all

Docs: https://docs.openclaw.ai/gateway/doctor, https://docs.openclaw.ai/tools/browser, https://docs.openclaw.ai/gateway/troubleshooting

If that fixes it, please right-click the solution message → Apps → ✅ Mark Solution.

nova furnace Apr 17, 2026, 11:50 AM

#

can you try x.com now?

I tried again, same result. X still only returns the generic error page, not tweet content.

So from here, no, I still can’t see the first tweet on x.com.

If you want a real result now, send me one of these:

• the exact profile URL
• a screenshot of the page
• or the page HTML/text from your browser session

Then I can tell you the first tweet immediately.

try again please

I already retried, and the blocker is the same: X is serving an error page to this environment, not actual tweet content.

Retrying the same fetch won’t magically change it. If you want, send me a profile URL or a screenshot, and I can still help from there.

browser chrome is open

Nice, but I still can’t control that Chrome session from this Telegram chat. Opening Chrome on your Mac does not automatically give me browser-driving access here.

If you want me to help with the first tweet right now, do one of these:

• send a screenshot of the X page
• send the profile URL and I’ll tell you what to look for
• paste the output of whatever openclaw browser ... command you’re using locally, and I’ll guide the next step

The missing piece is browser control, not whether Chrome is open.

bitter violetBOT Apr 17, 2026, 11:51 AM

#

Yep, if your real Chrome is already open, don’t use --browser-profile openclaw for this.

openclaw = isolated managed browser
user = attach to your already-open Chrome session

So for X, try the user profile instead:

In Chrome, open:

chrome://inspect/#remote-debugging

Turn on remote debugging, keep Chrome open, and accept the attach prompt if it appears.

Then run:

#

openclaw browser --browser-profile user start
openclaw browser --browser-profile user status
openclaw browser --browser-profile user tabs
openclaw browser --browser-profile user snapshot --format ai

What you want to see:

status shows driver: existing-session
status shows transport: chrome-mcp
tabs lists your current Chrome tabs

If that works, OpenClaw is attached to your live Chrome session, which is the right path for testing X.

If it still fails, paste just this output next:

#

openclaw browser --browser-profile user status

Docs: https://docs.openclaw.ai/tools/browser and https://docs.openclaw.ai/help/faq

If this solved it, please right-click the solution message → Apps → ✅ Mark Solution.

nova furnace Apr 17, 2026, 11:56 AM

#

browser chrome is open

Nice, but I still can’t control that Chrome session from this Telegram chat. Opening Chrome on your Mac does not automatically give me browser-driving access here.

If you want me to help with the first tweet right now, do one of these:

• send a screenshot of the X page
• send the profile URL and I’ll tell you what to look for
• paste the output of whatever openclaw browser ... command you’re using locally, and I’ll guide the next step

The missing piece is browser control, not whether Chrome is open.

can you check again?

I can’t, not in the way you mean. I still don’t have a browser-control tool attached to this chat, so I cannot inspect your open Chrome window.

If you want a real answer now, send a screenshot of the X page. I’ll read the first tweet immediately.

please try again, chrome is up on x.com

I get why you’re pushing on this, but the limit isn’t whether Chrome is open. The limit is that this chat session has no browser-control connection to your local Chrome.

So no, I still can’t read the first tweet from your open browser from here.

Fastest working path:

• send me a screenshot, or
• paste the exact OpenClaw browser command/session output you started locally, and I’ll help attach to it if your setup supports that.

bitter violetBOT Apr 17, 2026, 11:57 AM

#

Not directly from Discord, no. But your local OpenClaw install should be able to, if it attaches to Chrome properly.

Since Chrome is already open on x.com, run these locally now:

openclaw browser --browser-profile user start
openclaw browser --browser-profile user status
openclaw browser --browser-profile user tabs

If tabs shows your x.com tab, you’re connected.

If it does not connect, do this in Chrome first:

chrome://inspect/#remote-debugging

#

Enable remote debugging, keep Chrome open, accept the attach prompt, then rerun the three commands above.

Most important bit: use user, not openclaw, if you want the already-open Chrome session.

Paste the output of this one if it still fails:

openclaw browser --browser-profile user status

nova furnace Apr 17, 2026, 11:59 AM

#

➜ ~ openclaw browser --browser-profile user tabs

🦞 OpenClaw 2026.4.15 (041266a) — I'm not magic—I'm just extremely persistent with retries and coping strategies.

│
◇

(untitled)
https://x.com/home
id: 2
(untitled)
chrome://inspect/#remote-debugging
id: 3
➜ ~ openclaw browser --browser-profile user status

🦞 OpenClaw 2026.4.15 (041266a) — iMessage green bubble energy, but for everyone.

│
◇
profile: user
enabled: true
running: true
transport: chrome-mcp
browser: unknown
detectedBrowser: chrome
detectedPath: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
profileColor: #00AA00
➜ ~

But still i can't read tweets asking telegram to do so

bitter violetBOT Apr 17, 2026, 12:00 PM

#

Perfect, that output proves the browser attach is working.

So the problem is not Chrome anymore. It’s now one of these:

your Telegram-facing agent is still defaulting to the openclaw browser profile instead of user
Telegram is talking to a different gateway/node than the one where Chrome is attached
the agent/tool policy is blocking the browser tool

The next thing I’d do is set the default browser profile to user:

openclaw config set browser.defaultProfile '"user"'
openclaw gateway restart

Then ask Telegram something explicit like:

#

use the browser tool and read the current x.com tab

If it still refuses, paste these:

openclaw config get browser.defaultProfile
openclaw config get plugins.allow
openclaw config get tools.allow
openclaw config get tools.deny

One important gotcha: Telegram can only use the browser on the same gateway/node that attached to Chrome. If your Telegram bot is hitting another machine, it won’t see this session.

Docs: https://docs.openclaw.ai/tools/browser and https://docs.openclaw.ai/gateway/troubleshooting

nova furnace Apr 17, 2026, 12:02 PM

#

➜ ~ openclaw gateway restart

🦞 OpenClaw 2026.4.15 (041266a) — I autocomplete your thoughts—just slower and with more API calls.

Restarted LaunchAgent: gui/501/ai.openclaw.gateway
➜ ~ openclaw config get browser.defaultProfile

🦞 OpenClaw 2026.4.15 (041266a) — I don't just autocomplete—I auto-commit (emotionally), then ask you to review (logically).

user
➜ ~ openclaw config get plugins.allow

🦞 OpenClaw 2026.4.15 (041266a) — Your terminal just grew claws—type something and let the bot pinch the busywork.

Config path not found: plugins.allow
➜ ~ openclaw config get tools.allow

🦞 OpenClaw 2026.4.15 (041266a) — Your AI assistant, now without the $3,499 headset.

Config path not found: tools.allow
➜ ~ openclaw config get tools.deny

🦞 OpenClaw 2026.4.15 (041266a) — If it works, it's automation; if it breaks, it's a "learning opportunity."

Config path not found: tools.deny
➜ ~

bitter violetBOT Apr 17, 2026, 12:03 PM

#

Those Config path not found lines are actually fine. They just mean you don’t have explicit allow/deny overrides set.

So at this point we know:

browser.defaultProfile = user
user profile is attached successfully
Chrome MCP is working
browser/tool allowlists are not obviously blocking it

So the remaining problem is most likely session/routing, not browser setup.

Two likely causes:

Telegram is connected to a different gateway/node than this Mac
the current Telegram conversation is stale and still stuck on the earlier “no browser connection” assumption

Best next test

#

Open a fresh Telegram conversation/session and say something very explicit:

Use the browser tool and tell me the title of my current tab.

At the same time, in a terminal run:

openclaw logs --follow

Then send that Telegram message.

What to look for

If logs show a browser tool call, the gateway is seeing the request
If logs show no browser activity, Telegram is probably hitting a different gateway/install
If the model still answers “I can’t access your browser” in the old chat, I’d strongly suspect stale session context

#openclaw browser --browser-profile openclaw start

Best next test

What to look for