Codex Desktop 26.609.71450 fails to hydrate existing local session and RAM reaches 99–100%

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

26.609.71450 About dialog shows: Version 26.609.71450 Released Jun 16, 2026

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Windows 11 Microsoft Windows NT 10.0.26200.0 x64 Codex Desktop from Microsoft Store

What issue are you seeing?

After the Microsoft Store update from OpenAI Codex Windows App 26.609.4994.0 to 26.609.9530.0, the app can now open the main window, but it is still practically unusable.

This looks like a new or incomplete Windows Desktop App regression.

Environment:

• Product: OpenAI Codex Windows Desktop App
• Version: 26.609.9530.0
• PackageFullName: OpenAI.Codex_26.609.9530.0_x64__2p2nqsd0c76g0
• InstallLocation: C:\Program Files\WindowsApps\OpenAI.Codex_26.609.9530.0_x64__2p2nqsd0c76g0
• Package status: Ok
• Platform: Microsoft Windows NT 10.0.26200.0 x64
• Subscription: ChatGPT Pro
• Setup: native Windows / PowerShell
• WSL is disabled / not used

Context:
This is a continuation of the previous Windows App issue I reported with 26.609.4994.0.

Before:

• OpenAI.Codex_26.609.4994.0_x64__2p2nqsd0c76g0
• The app did not open the main window properly.

After Microsoft Store update:

• OpenAI.Codex_26.609.9530.0_x64__2p2nqsd0c76g0
• The main window opens after 3 minutes waiting period, but the app immediately becomes extremely heavy and difficult to use.

Actual behavior:

• Codex opens the main window.
• it was 3 minute in a tray unresponsive, after it, RAM usage rises extremely high.
• I observed RAM around 87–99% in Process Lasso / system overlay.
• I had to close Codex manually because the machine became too loaded to work normally. (waited 15 min)
• This did not happen about a month ago.
• I did not intentionally resume the old queue before seeing the high memory pressure.
• Codex appears to auto-load a previous project/thread/queue state on startup.
• The UI shows a previous threads
• The UI shows “Queue paused because you interrupted”.
• The queue contains many old queued items. (in fact 10 days ago i deleted all my valuable old sessions expecting it could help and created new, projects and new chats and now it becomes one week old and it does not load up)
• The UI becomes very slow / effectively unusable.
• I cannot reliably start new work or continue existing work.

Expected behavior:

• Codex should open normally after the update.
• Startup should not push RAM to 87–99%.
• The UI should remain responsive.
• Previous queue/session state should not automatically make the app unusable.
• There should be a safe way to stop, clear, or quarantine a broken local queue/session state without deleting all .codex data.
• The app should not require deleting local history or sessions to recover from a bad state.

Diagnostics:

• AppX package status is Ok.
• CODEX_CLI_PATH is empty in User, Machine, and Process scopes.
• Bundled codex.exe exists at:

C:\Program Files\WindowsApps\OpenAI.Codex_26.609.9530.0_x64__2p2nqsd0c76g0\app\resources\codex.exe

• Bundled codex.exe file exists and has size:

280,658,224 bytes

• LastWriteTime:

6/12/2026 12:51:21 AM

• Directly running the bundled codex.exe from PowerShell returns Access denied, likely because it is inside the protected WindowsApps package directory.
• I searched local .codex session files and found many repeated matches inside:

C:\Users\myname.codex\sessions\2026\06\08\rollout-2026-06-08T23-29-25-019ea923-f0d4-7af0-bb96-2a041cff17e5.jsonl

• The repeated matches include old queue/project/task content

Impact:
This is still a complete blocker.

I am paying for ChatGPT Pro, but I cannot use the Codex Windows Desktop App reliably. The previous build did not open correctly. The new build opens, but startup memory usage and old queue/session auto-loading make it unusable.

Request:
Please investigate Codex Windows App 26.609.9530.0 as a Windows Desktop App startup / memory / queue-state regression.

Please provide:

• a working hotfix build,
• a rollback path to a known stable Windows build,
• a safe way to clear or quarantine a broken local queue/session state without deleting all .codex data,
• a safe way to disable automatic queue/session restore on startup,
• and guidance on how to collect useful logs without exposing private project data, auth files, or full session transcripts.

What steps can reproduce the bug?

1. Launch Codex Desktop on Windows.
2. Wait for the app to open. Cold start took approximately 3 minutes.
3. Open an existing project from the sidebar.
4. Open an existing thread (any I have more than 5)
5. Observe that the main thread body does not load.
6. Observe that the old queued prompts are still visible in the queue panel.
7. Observe that the right panel shows “No artifacts yet” and “No sources yet”.
8. Keep the thread open for a few minutes.
9. RAM usage climbs from around 44% to 87%, then 99–100%.
10. Close Codex to prevent the system from becoming fully unstable.

I did not press Resume

Laptop Asus Zenbook 14, i9-185h, 32gb ram
month's ago it was flied as a Ferrari that was soo good

What is the expected behavior?

_No response_

Additional information

_No response_