Codex App fails to read recent conversation #24173

Activity

1. funct7

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on May 23, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   sessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving

   on May 23, 2026
3. github-actions commented on May 23, 2026

   

   github-actionsBot

   on May 23, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Codex Desktop 26.519.22136: local project conversation history missing after update, threads still exist in state_5.sqlite #23979
   • Codex Desktop sidebar chat history disappears and latest update does not restore hidden chats #23999
   • Codex App session list can hide sessions whose first user message is an empty diff-comment wrapper #24077
   • Codex Desktop project sidebar shows No chats while local sessions still exist #22796
   • Codex Desktop sidebar project groups only show threads from the first recent page; expanding a project does not load remaining project threads #23825

   Powered by Codex Action
4. diegobonacolsi commented on Jul 7, 2026

   

   diegobonacolsi

   on Jul 7, 2026

   More actions

   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.