Windows: WSL backend disables Chrome/Edge control with misleading organization/region message

Environment

• Codex Desktop release: 26.903.61454
• OS: Windows with WSL backend enabled
• Subscription: Personal Pro

Problem

When Codex uses the WSL backend, both Google Chrome and Microsoft Edge are disabled in Settings → Computer use, with this message:

Disabled by your organization or unavailable in your region

Switching to the Windows backend makes both browser controls available and allows proceeding with plugin installation. Switching back to WSL reproduces the disabled state.

The desktop logs explicitly identify the reason as wsl-disabled, but the UI does not mention WSL.

Steps to reproduce

1. Run Codex Desktop on Windows.
2. Enable the WSL agent backend.
3. Open Settings → Computer use.
4. Observe that Chrome and Edge are disabled with the organization/region message.
5. Switch the agent backend to Windows.
6. Observe that both browser controls become available.
7. Switch back to WSL and observe that they are disabled again.

Relevant logs

The same desktop release logged both states:

2026-09-09T17:00:39.641Z
browser_use_availability_resolved available=true browserPane=true platform=Windows reason=available release=26.903.61454

2026-09-09T17:17:47.159Z
browser_use_availability_resolved available=false browserPane=true platform=Windows reason=wsl-disabled release=26.903.61454

Expected behavior

Browser control should work with a WSL agent backend through the Windows desktop app.

If this combination is currently unsupported, the UI should explicitly explain the WSL limitation instead of displaying an organization/region error.

Switching the entire agent backend is disruptive: in this reproduction, the existing WSL session could not be continued under the Windows backend, requiring a switch back to WSL to resume the conversation.

Related issue

#25301 reports the same reason=wsl-disabled behavior on an older release. This report confirms it on 26.903.61454, with a reproducible Windows-versus-WSL comparison for Chrome and Edge.

Start in Settings → Computer use and trace the browser availability state that produces browser_use_availability_resolved, comparing the Windows and WSL backend cases. Review related issue #25301 and verify that the result either enables Chrome and Edge under WSL or clearly identifies the WSL limitation instead of showing an organization or region error.