Desktop upgrade to 26.715.72359 hides existing thread even though it is resumable and indexed
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with the migration and indexing behavior around ~/.codex/sessions and session_index.jsonl, using the reported thread as a reference. Reproduce the upgrade on Windows 11 and verify that codex resume still works while the thread is absent from the new UI. Done means existing indexed sessions appear in the project view after upgrading.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.715.72359
What subscription do you have?
Pro
What platform is your computer?
Windows 11
What issue are you seeing?
My Chatgpt account is with sindhu.madalansr@gmail.com
What version of the Codex App are you using?
ChatGPT (Powered by Codex & OWL)
Version: 26.715.72359
Released: Jul 22, 2026
Windows 11
What subscription do you have?
ChatGPT Plus
What issue are you seeing?
After accepting the in-app "Upgrade available" prompt, the application restarted automatically and migrated to the new project-based UI.
My primary long-running development conversation disappeared from the sidebar.
However, the conversation has NOT been lost.
Evidence:
- The session file still exists in ~/.codex/sessions.
- session_index.jsonl still contains the thread.
- The thread can be resumed successfully using:
codex resume 019f75ea-c4aa-7e62-8afd-e398f05326a7
The complete conversation, tool calls and history are still present.
The new desktop UI simply does not display the thread.
Expected behavior
After upgrading, existing conversations should appear in the new UI exactly as before.
If migration is required, legacy sessions should be imported into the new project view.
Actual behavior
The upgraded UI hides the existing thread.
The CLI can resume it successfully, proving the session still exists.
Steps to reproduce
- Use Codex Desktop/Web UI for several days.
- Create a long-running development thread.
- Accept the in-app "Upgrade available".
- Allow the app to restart automatically.
- Observe that the thread disappears from the sidebar.
- Run:
codex resume
The thread resumes successfully.
Additional information
Thread ID:
019f75ea-c4aa-7e62-8afd-e398f05326a7
The corresponding rollout session still exists and is approximately 32 MB.
session_index.jsonl still references the thread.
This appears to be a desktop migration/indexing issue rather than data loss.
What steps can reproduce the bug?
What version of the Codex App are you using?
ChatGPT (Powered by Codex & OWL)
Version: 26.715.72359
Released: Jul 22, 2026
Windows 11
What subscription do you have?
ChatGPT Plus
What issue are you seeing?
After accepting the in-app "Upgrade available" prompt, the application restarted automatically and migrated to the new project-based UI.
My primary long-running development conversation disappeared from the sidebar.
However, the conversation has NOT been lost.
Evidence:
- The session file still exists in ~/.codex/sessions.
- session_index.jsonl still contains the thread.
- The thread can be resumed successfully using:
codex resume 019f75ea-c4aa-7e62-8afd-e398f05326a7
The complete conversation, tool calls and history are still present.
The new desktop UI simply does not display the thread.
Expected behavior
After upgrading, existing conversations should appear in the new UI exactly as before.
If migration is required, legacy sessions should be imported into the new project view.
Actual behavior
The upgraded UI hides the existing thread.
The CLI can resume it successfully, proving the session still exists.
Steps to reproduce
- Use Codex Desktop/Web UI for several days.
- Create a long-running development thread.
- Accept the in-app "Upgrade available".
- Allow the app to restart automatically.
- Observe that the thread disappears from the sidebar.
- Run:
codex resume
The thread resumes successfully.
Additional information
Thread ID:
019f75ea-c4aa-7e62-8afd-e398f05326a7
The corresponding rollout session still exists and is approximately 32 MB.
session_index.jsonl still references the thread.
This appears to be a desktop migration/indexing issue rather than data loss.
What is the expected behavior?
No response
Additional information
No response
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·