Desktop upgrade to 26.715.72359 hides existing thread even though it is resumable and indexed

Open 💬 1 comment Opened Jul 23, 2026 by Rajesh778484
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

  1. Use Codex Desktop/Web UI for several days.
  2. Create a long-running development thread.
  3. Accept the in-app "Upgrade available".
  4. Allow the app to restart automatically.
  5. Observe that the thread disappears from the sidebar.
  6. Run:

codex resume <thread-id>

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

  1. Use Codex Desktop/Web UI for several days.
  2. Create a long-running development thread.
  3. Accept the in-app "Upgrade available".
  4. Allow the app to restart automatically.
  5. Observe that the thread disappears from the sidebar.
  6. Run:

codex resume <thread-id>

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_

View original on GitHub ↗

1 Comment

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #33774
  • #33652
  • #33727
  • #34754

Powered by Codex Action