Codex App fails to read recent conversation

Open 💬 2 comments Opened May 23, 2026 by funct7
💡 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.519.41501 (3044)

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

Before I updated the app about 10 minutes ago, I was using the app just fine, but after the update, the recent history was gone. The CLI still shows it, but the app doesn't, and the VS Code extension also doesn't show the recent history.

What steps can reproduce the bug?

Opening the same chat session in Codex CLI, the app, and the VS code extension.

What is the expected behavior?

The chat history up to the most recent message should be displayed in all three interfaces.

Additional information

  • CLI version: codex-cli 0.133.0
  • Thread (Feedback) ID: 019e51a1-d6da-7a03-a27f-c61ddf539144

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 3 months ago

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

  • #23979
  • #23999
  • #24077
  • #22796
  • #23825

Powered by Codex Action

diegobonacolsi · 1 month ago

Same thing here, I've found a workaround to recover lost chats. Below is my conclusion drafted with Codex itself.

Root cause: the normal thread/list filesystem scan skipped sessions whose rollout started with an empty ## My request for Codex: wrapper. The threads were still present in SQLite, thread/read and codex resume worked, and thread/list with useStateDbOnly: true returned them correctly.

Workaround: after backing up the rollout JSONL, I changed the empty wrapper to ## My request for Codex:. (added a single period). Both missing threads immediately reappeared in the Codex UI.

This seems most likely when a new thread starts from pasted/attached context without an actual text instruction in the first message.