Bug

When browser.cdpUrl is set in config (e.g. http://localhost:9222), the browser tool ignores it and still looks for the DevToolsActivePort file at the default Chrome profile path.

Config

{
  "browser": {
    "enabled": true,
    "cdpUrl": "http://localhost:9222",
    "attachOnly": false,
    "defaultProfile": "user"
  }
}

Expected behavior

When cdpUrl is set, connect directly to that URL without checking for DevToolsActivePort.

Actual behavior

Error: Could not find DevToolsActivePort for chrome at /Users/clawdbot/Library/Application Support/Google/Chrome/DevToolsActivePort

Context

• Chrome v145 running with --remote-debugging-port=9222 and a custom --user-data-dir
• Port 9222 responds correctly: curl http://localhost:9222/json/version returns valid JSON
• Chrome does NOT write DevToolsActivePort to the custom user-data-dir
• OpenClaw v2026.3.13
• macOS 15.3 (arm64)