#Error: Error: Browser attachOnly is enabled and profile "openclaw" is not running.

1 messages · Page 1 of 1 (latest)

dull topaz
#

Error: Error: Browser attachOnly is enabled and profile "openclaw" is not running.

severe citrusBOT
#

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

severe parrotBOT
#

That error is almost always just this:

  • You have browser.attachOnly: true
  • You’re trying to use the managed profile openclaw
  • But in attach-only mode OpenClaw will never launch the local managed browser, so openclaw won’t be “running” unless you started a CDP target yourself.

Docs: https://docs.openclaw.ai/tools/browser (see attachOnly)

Fix options

Option A (most common): use the managed openclaw browser

  1. Set attachOnly back to false (default):
openclaw config set browser.attachOnly false
openclaw gateway restart
#
  1. Start the browser profile:
openclaw browser start --browser-profile openclaw
openclaw browser status

Option B: you actually wanted “take over my existing Chrome”

Keep attachOnly: true, but then you must use profile="chrome" and have the Browser Relay extension attached to a tab (badge ON). If no tab is attached you’ll get similar “not reachable / not running” style errors.

Docs: https://docs.openclaw.ai/tools/chrome-extension

If you paste these, I can tell you which path you’re on

openclaw --version
openclaw config get browser.attachOnly
openclaw config get browser.defaultProfile
# 
openclaw browser profiles
openclaw browser status