Dev Tools · 1h ago
WSL2 browser automation: CDP over NAT is the real gotcha
A developer documents the pitfalls of running browser automation from WSL2, finding that WSL2's default NAT networking breaks localhost connections to Windows Chrome. The fix is to use the Windows host IP from WSL2 or switch to mirrored networking. The fastest reliable setup runs both agent and browser in the same Linux environment via WSLg.
Meridian48 take
This is a practical debugging story, not a breakthrough — but it highlights how WSL2's networking quirks still trip up developers who assume seamless cross-OS tooling.
Read the full reporting
I wasted a weekend on WSL2 browser automation so you don’t have to →
DEV Community
wsl2browser-automation