Windows app fails to start in WSL mode when bundled bwrap is missing

Bug report

Summary

The Windows Codex app fails to start when Run Codex in Windows Subsystem for Linux is enabled.

The app shows:

Codex app-server initialize handshake timed out

Environment

• Codex Windows App package: OpenAI.Codex_26.721.4979.0_x64__2p2nqsd0c76g0
• Platform: Windows
• WSL: WSL 2
• Default distribution: Ubuntu 24.04
• Reproduced on: 2026-07-26

Reproduction

1. Enable runCodexInWindowsSubsystemForLinux = true.
2. Launch the Codex Windows App.
3. Wait for startup.

Expected behavior

The app-server starts inside WSL and completes the initialization handshake.

Actual behavior

Startup fails after approximately 30 seconds with:

Codex app-server initialize handshake timed out

Evidence

The desktop log reports that Ubuntu is available and running, then starts the process through wsl.exe. Before the handshake timeout, it reports:

bundled_executable_relocation_failed
executableName=bwrap
errorCode=ENOENT
sourcePath=...\\resources\\codex-resources\\bwrap

The same installation does not contain the resources\\codex-resources directory or the bwrap executable. The subsequent WSL stdio transport is created, but the app-server never responds to the initialization request within 30 seconds.

Relevant log sequence:

• Spawning process inside WSL
• Bundled executable relocation failed ... bwrap ... ENOENT
• stdio_transport_spawned ... spawnCommand=wsl.exe
• initialize_handshake_timeout durationMs=30012

This suggests the Windows package is missing a WSL runtime resource or the resource relocation path is incorrect.