Browser Use not available on Windows 11 WSL: no node_repl tool or browser-use socket

What version of the Codex App are you using (From “About Codex” dialog)?

26.429.61741

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

Browser Use does not work in Codex Desktop on Windows 11 + WSL2.

When I ask Codex to open a browser, the Browser Use skill is selected, but the required runtime/tool is missing. The active session does not expose mcp__node_repl__js, which Browser Use requires.

The Browser Use plugin is enabled in config:

[plugins."browser-use@openai-bundled"]
enabled = true
But there is no browser-use backend socket in WSL /tmp.

Observed output:

/mnt/c/Users/yby/.codex/bin/wsl/codex --version
# codex-cli 0.128.0-alpha.1

ls -la /tmp | grep -E 'codex-browser-use|browser-use'
# no output
Earlier direct bootstrap testing of the Browser Use client produced:

Failed to connect to browser-use backend "iab". No current Codex session metadata was available, so IAB ownership could not be checked. Discovery diagnostics: listedPipes=0, candidates=2, browsers=0, iabBrowsers=0, failures=["legacy-iab/connect/Error","legacy-chrome/connect/Error"], pipeListingError=Error: ENOENT.
Reinstalling Codex Desktop and deleting/renaming the Windows Codex cache did not fix it. Codex Desktop recreated the WSL bridge, but it still reports codex-cli 0.128.0-alpha.1 and Browser Use still has no socket/runtime.

### What steps can reproduce the bug?


```markdown
1. Use Codex Desktop on Windows 11 with WSL2.
2. Enable the bundled Browser Use plugin.
3. Start a fresh Codex Desktop thread in a WSL workspace.
4. Ask:

```text
open browser to https://example.com
Codex attempts to use Browser Use, but the required mcp__node_repl__js tool is not available in the session.
In WSL, check:
/mnt/c/Users/yby/.codex/bin/wsl/codex --version
ls -la /tmp | grep -E 'codex-browser-use|browser-use'
Actual output:

codex-cli 0.128.0-alpha.1
# no browser-use socket output
I also tried:

Restarting Codex Desktop
Starting fresh threads
Reinstalling Codex Desktop
Renaming/deleting C:\Users\<user>\.codex\bin
Renaming/deleting C:\Users\<user>\.codex\.tmp
Letting Codex Desktop recreate the WSL bridge
The issue persists.

### What is the expected behavior?

```markdown
Browser Use should initialize successfully in Codex Desktop.

Expected:
- The session exposes the required Node REPL tool, typically `mcp__node_repl__js`.
- Codex Desktop starts the Browser Use IAB backend for the active session.
- A browser-use socket appears in WSL `/tmp`, such as a `codex-browser-use...` socket.
- A prompt like `open browser to https://example.com` opens/navigates the in-app browser.

### Additional information

Environment:
- Windows 11
- WSL2
- Codex Desktop
- WSL bridge binary: `/mnt/c/Users/<user>/.codex/bin/wsl/codex`
- WSL bridge version: `codex-cli 0.128.0-alpha.1`

The plugin files exist and Browser Use is enabled, so this does not appear to be a missing plugin install. It looks like the Desktop runtime is not injecting/starting the Browser Use runtime pieces for WSL sessions: no `mcp__node_repl__js` tool and no Browser Use IAB socket.