Windows/WSL regression: Integrated Terminal no longer opens; first failure observed on 26.730, persists on 26.803

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

26.803.41515

About UI shows:

ChatGPT — Powered by Codex & OWL
Version 26.803.41515
Released Aug 7, 2026

The currently installed Microsoft Store/AppX package is:

OpenAI.Codex_26.803.5235.0_x64__2p2nqsd0c76g0

So there is also a discrepancy between the version shown in the About UI (26.803.41515) and the installed AppX package version (26.803.5235.0).

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 10 Pro, 64-bit
Windows version: 2009
OS build: 19045

WSL2:

• Ubuntu 24.04
• Git 2.43.0
• bubblewrap 0.9.0 at /usr/bin/bwrap

What issue are you seeing?

The Codex Desktop integrated terminal no longer opens.

With:

Agent Environment: Windows Subsystem for Linux
Integrated Terminal: WSL

clicking Terminal does not open a usable terminal panel or terminal session.

I also tested:

Agent Environment: Windows native
Integrated Terminal: PowerShell

and clicking Terminal still does not open a terminal.

This is a regression. I was using the integrated terminal successfully several days before the update sequence described below.

Windows AppX deployment history shows this version timeline:

26.727.4816.0 — active from July 31, 2026 until August 5, 2026
26.730.8199.0 — installed August 5, 2026
26.803.5235.0 — staged beginning August 7, 2026 and registered as the update on August 8, 2026

My known-good usage was during the 26.727.4816.0 period.

The earliest explicit terminal-attachment failure I found in the retained Codex Desktop logs is under 26.730.8199.0:

2026-08-06T19:44:50.750Z

The logged result is:

No app terminal session is attached to this thread yet.
success=false

The same terminal-session attachment failure appears again in later logs under subsequent builds.

What steps can reproduce the bug?

1. Run Codex Desktop on Windows with a working WSL2 Ubuntu installation.
2. Configure:

Agent Environment: Windows Subsystem for Linux
Integrated Terminal: WSL

1. Open a project/worktree located in WSL.
2. Click Terminal.
3. No usable terminal panel/session opens.
4. Change the configuration to:

Agent Environment: Windows native
Integrated Terminal: PowerShell

1. Click Terminal again.
2. The integrated terminal still does not open.

No project-specific code is required to reproduce the terminal UI/session failure.

What is the expected behavior?

When the Agent Environment is WSL and Integrated Terminal is WSL, clicking Terminal should create, attach, and display a usable WSL terminal session for the current project/worktree.

When configured for Windows native + PowerShell, the integrated PowerShell terminal should likewise open normally.

Additional information

WSL itself appears healthy.

From ordinary WSL:

command -v bwrap
/usr/bin/bwrap

and:

bwrap --version
bubblewrap 0.9.0

Git also exists and works normally from ordinary WSL.

Codex Desktop logs repeatedly contain:

bundled_executable_relocation_failed
errorCode=ENOENT

for a bundled helper source corresponding to:

...\app\resources\codex-resources\bwrap

and a destination corresponding to:

C:\Users\<USER>\.codex\bin\wsl\codex-resources\bwrap

The currently installed 26.803.5235.0 Microsoft Store package reports:

Status: Ok

but does not contain:

app\resources\codex-resources

Importantly, the same bundled bwrap relocation warning was already present in retained logs from 26.727.4816.0, when I remember the integrated terminal working normally. Therefore the missing bundled bwrap appears to be relevant diagnostic evidence, but it may not by itself explain the integrated-terminal regression.

The Desktop logs also contain repeated:

Git is unavailable

messages even though Git works normally inside ordinary WSL.

A retained log under 26.730.8199.0 also shows Codex attempting to enter WSL:

[spawn-async] Spawning process inside WSL

followed by Git discovery failures.

Troubleshooting already performed

I fully restarted Windows and the application.

I uninstalled the older ChatGPT Classic application to eliminate it as a possible conflict. This had no effect.

I used:

Windows Settings → Apps → ChatGPT → Repair

Repair completed successfully but had no effect.

After Repair, the installed package remained:

OpenAI.Codex_26.803.5235.0_x64__2p2nqsd0c76g0
Status: Ok

and:

app\resources\codex-resources

was still absent.

I then performed a full controlled uninstall of the current ChatGPT/Codex application, restarted Windows, and reinstalled it fresh from Microsoft Store.

The clean Store reinstall again installed exactly:

OpenAI.Codex_26.803.5235.0_x64__2p2nqsd0c76g0

The package again reported:

Status: Ok

and app\resources\codex-resources was still absent.

The integrated terminal still does not open after the clean reinstall.

I also searched the local machine for the previous 26.727.4816.0 MSIX/AppX payload, but the old signed installer is no longer locally available, so I have not attempted an unsupported downgrade from a third-party source.

Regression timeline

Windows AppX deployment history gives the following useful boundary:

26.727.4816.0
31 Jul – 5 Aug
Known-good integrated-terminal usage from my own use

26.730.8199.0
5 Aug – 8 Aug
Earliest retained explicit terminal-attachment failure:
2026-08-06T19:44:50.750Z

26.803.5235.0
8 Aug onward
Terminal remains unusable
Repair and clean Store reinstall do not resolve it

This suggests the terminal regression occurred no later than the 26.730.8199.0 period.

Possibly related issues

• #25225 — Windows Desktop integrated-terminal lifecycle problems; Windows-native terminal cannot open, but WSL terminal could still open in that report.
• #25256 — Windows bottom/integrated terminal panel flashes and disappears.
• #29070 — terminal UI exists but read_thread_terminal reports no attached session.

My case differs because the integrated Terminal UI does not open into a usable session at all in either WSL or Windows-native mode, and the problem persists through Repair and a clean Microsoft Store reinstall.

I have retained the full Codex Desktop logs covering the known-good and failing version periods. I am not uploading the complete raw logs publicly because they contain local paths, project/repository information, prompts, thread identifiers, and tool output. I can provide additional sanitized excerpts or private diagnostic information if needed.