Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

On WSL2, OpenClaw Gateway can reach the Windows Edge CDP endpoint successfully. Both /json/version and /json/list work, and /json/list shows a live type: "page" target with a normal HTTPS URL. However, OpenClaw still reports the remote attach-only profile as running: false, tabs returns No tabs, and snapshot fails with Browser attachOnly is enabled and profile "remote" is not running.

Steps to reproduce

Environment:

OpenClaw 2026.4.10
Gateway in WSL2
Microsoft Edge on Windows
Remote CDP on port 9222

Config:

"browser": {
"enabled": true,
"defaultProfile": "remote",
"profiles": {
"remote": {
"cdpUrl": "http://127.0.0.1:9222",
"attachOnly": true,
"color": "#00AA00"
}
}
}

I also tested:

"cdpUrl": "ws://127.0.0.1:9222/devtools/browser/"

with the same result.

Expected behavior

If /json/list already exposes a live page target, the remote attach-only profile should become usable for tabs / snapshot, or at least fail with a more specific attach/WebSocket error.

Actual behavior

curl http://127.0.0.1:9222/json/version succeeds.
curl http://127.0.0.1:9222/json/list succeeds.
/json/list includes a real page target like https://www.naver.com/ with type: "page".
openclaw browser --browser-profile remote status shows:
running: false
browser: unknown
detectedBrowser: unknown
openclaw browser --browser-profile remote tabs says:
No tabs (browser closed or no targets).
openclaw browser --browser-profile remote snapshot fails with:
Browser attachOnly is enabled and profile "remote" is not running.

OpenClaw version

2026.4.10

Operating system

Windows 11

Install method

wsl2 npm global

Model

openai-codex/gpt-5.2

Provider / routing chain

WSL2 OpenClaw Gateway -> browser plugin (remote attachOnly profile) -> CDP endpoint at 127.0.0.1:9222 -> Microsoft Edge on Windows host

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response