Codex Desktop cannot reopen multiple local sessions after model reliability regression

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

Codex app version: 26.506.3741.0

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows 11 Pro 10.0.26200 x64 HP Pavilion Gaming Laptop 15-dk1xxx PowerShell 7.6.1

What issue are you seeing?

I rely on Codex for real daily development work.

I recently experienced a noticeable Codex/model reliability regression. During the same period, I renewed my USD 200/month ChatGPT Pro plan because I initially believed the problem might be specific to my setup or workflow.

Now I also have three real work sessions that exist locally on disk, but Codex Desktop cannot reopen them. When I try to open them, the app only shows a generic error screen:

Ocurrió un error

The only visible options are:

• Comprobar actualizaciones
• Inténtalo nuevamente

Retrying does not solve the problem.

Affected session IDs:

• 019e30c2-dac0-7701-961f-538df19e3b8b
• 019e30cf-72da-7c53-928d-12c9b6b9049e
• 019e30d1-a348-72c0-9d61-9a1b1171a24a

Local files:

• C:\Users\Pc\.codex\sessions\2026\05\16\rollout-2026-05-16T09-28-56-019e30c2-dac0-7701-961f-538df19e3b8b.jsonl
• C:\Users\Pc\.codex\sessions\2026\05\16\rollout-2026-05-16T09-42-42-019e30cf-72da-7c53-928d-12c9b6b9049e.jsonl
• C:\Users\Pc\.codex\sessions\2026\05\16\rollout-2026-05-16T09-45-05-019e30d1-a348-72c0-9d61-9a1b1171a24a.jsonl

These are real production-style sessions from:

• C:\Clientes\Lunas Confort

They involved Supabase SQL, GitHub commits/pushes, business-critical fixes, verification steps, and work on a dirty repository where unrelated local changes had to be preserved.

This makes Codex very hard to rely on: I cannot fully trust the model behavior during the affected period, and I also cannot reopen the sessions where the problems happened.

What steps can reproduce the bug?

1. Open Codex Desktop on Windows.
2. Go to recent/local sessions.
3. Try to open any of these existing local sessions:

• 019e30c2-dac0-7701-961f-538df19e3b8b
• 019e30cf-72da-7c53-928d-12c9b6b9049e
• 019e30d1-a348-72c0-9d61-9a1b1171a24a

1. Codex Desktop shows a generic error screen:

Ocurrió un error

The local .jsonl files exist on disk, but the app cannot reopen them.

I do not know the exact token/context usage because the app fails before opening the sessions.

What is the expected behavior?

Codex Desktop should reopen local sessions that exist on disk, or show a specific recoverable error explaining why a session cannot be loaded.

At minimum, the app should provide enough diagnostic information to understand whether the session file is corrupted, too large, incompatible with the current app version, or affected by a known Codex Desktop issue.

Additional information

This issue may be related to the broader Codex/model reliability regression discussed in #21375 and my previous report #21942.

What I need is a concrete recovery or escalation path:

• Why these local sessions cannot be opened.
• Whether the sessions can be recovered.
• Whether this is related to the recent model/app reliability issues.
• Whether my Codex installation/account is affected by a known problem.
• What I should do next to make Codex reliable again.

If this cannot be resolved, I also need guidance on refund or billing adjustment options, because I renewed the USD 200/month plan while believing the problem might be local to me, but later saw strong evidence that many users were affected by similar Codex reliability regressions.