Description
When running bb-browser daemon in WSL2 (Windows Subsystem for Linux), it would be great to connect to the Windows hosts Chrome instance directly, so that the users real browser login state (cookies, sessions) can be leveraged.
Current situation
- Running
chrome.exe --remote-debugging-port=19825 --headless from inside WSL starts Chrome on Windows side
- WSL2 has network isolation - the CDP WebSocket port is not reachable from WSL via
127.0.0.1
- Using Puppeteers bundled Chrome in WSL works but is headless-only, losing real browser login state
Suggested approach
Document how to set up Chrome on Windows with --remote-debugging-port and make it accessible from WSL2. Options:
netsh interface portproxy to forward from WSLs virtual NIC- Windows Firewall rule to allow WSL2 subnet access to CDP port
- Auto-detect WSL2 host IP in daemon
Environment
- WSL2 + Ubuntu 22.04
- Chrome at
C:\\Users\\Administrator\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe
- bb-browser v0.11.3
Description
When running bb-browser daemon in WSL2 (Windows Subsystem for Linux), it would be great to connect to the Windows hosts Chrome instance directly, so that the users real browser login state (cookies, sessions) can be leveraged.
Current situation
chrome.exe --remote-debugging-port=19825 --headlessfrom inside WSL starts Chrome on Windows side127.0.0.1Suggested approach
Document how to set up Chrome on Windows with
--remote-debugging-portand make it accessible from WSL2. Options:netsh interface portproxyto forward from WSLs virtual NICEnvironment
C:\\Users\\Administrator\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe