Codex app has no access to @Browser or @Chrome on Windows in WSL mode.
Open 💬 2 comments Opened Jul 26, 2026 by Perdolique
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
26.721.41059
What subscription do you have?
Pro
What platform is your computer?
Windows 11
What issue are you seeing?
Codex app has no access to @Browser or @Chrome on Windows in WSL mode. It's impossible to use such tools at all.
What steps can reproduce the bug?
Feedback ID: 019f9ef1-395c-72f3-8e0b-c765c6c26f72
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This looks like the current Codex Desktop/WSL bridge limitation rather than a problem with your Chrome profile. One workaround is to bypass the bundled @Chrome bridge and connect a WSL-side
chrome-devtools-mcpprocess to a dedicated Windows Chrome debug profile.Start Windows Chrome with
--remote-debugging-port=9222and a separate--user-data-dir, then verify from WSL withcurl http://127.0.0.1:9222/json/version(use the Windows host IP if WSL loopback forwarding is unavailable). Point the MCP config at that reachable browser URL and restart Codex.Disclosure: I maintain a small paid installer/docs package for this exact WSL-to-Windows setup, so I can share it if useful; the manual checks above are enough to validate whether the route will work first.