fix(browser): diagnose empty WSL2 Chrome replies (#100590)

* fix(browser): diagnose Windows CDP listener mismatch

Base the repair on #93481 while matching Chromium's IPv4-first, IPv6-fallback listener contract and keeping CDP exposure loopback-scoped.

Co-authored-by: ZengWen-DT <ceng.wen@xydigit.com>

* style(docs): format browser troubleshooting table

* docs: refresh browser troubleshooting map

* fix(browser): diagnose reset CDP replies

* docs: refresh browser troubleshooting map

---------

Co-authored-by: ZengWen-DT <ceng.wen@xydigit.com>
This commit is contained in:
Peter Steinberger 2026-07-06 07:42:02 +01:00 committed by GitHub
parent 5713f1bec1
commit 2830b3ef38
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 107 additions and 17 deletions

View file

@ -8967,6 +8967,7 @@ Do not edit it by hand; run `pnpm docs:map:gen`.
- H2: Critical rule for the Control UI
- H2: Validate in layers
- H3: Layer 1: verify Chrome is serving CDP on Windows
- H4: Diagnose IPv4 and IPv6 before changing portproxy
- H3: Layer 2: verify WSL2 can reach that Windows endpoint
- H3: Layer 3: configure the correct browser profile
- H3: Layer 4: verify the Control UI layer separately
@ -9497,6 +9498,7 @@ Do not edit it by hand; run `pnpm docs:map:gen`.
- H2: Storage
- H2: Limits
- H2: Troubleshooting
- H3: Tool-policy diagnostic
- H2: Related
## tools/skills-config.md