Codex App: Working Threads Missing After Latest Update
What version of the Codex App are you using (From “About Codex” dialog)?
260203.1501 (523)
What subscription do you have?
Plus
What issue are you seeing?
After updating the codex app this morning approx 12 hours ago, the threads in 4 different projects I was working on at the time, are all missing. It just says "No Threads". I had been working in those threads for most of the day yesterday and this morning before the update.
I have checked Settings > Archived Threads and the missing threads are not there. The previously archived threads are all present though.
I have closed the app and restarted my machine a few times and they do not appear.
I thought I'd give it some time but nothing has shown and I did not want to start again as there was a lot of context in each of the threads for what I was working on at the time.
What steps can reproduce the bug?
The only thing I did was click the blue update button on the top left of the screen when it showed this morning. After updating, the threads were all missing.
What is the expected behavior?
Threads I was working on prior to the update to show.
Additional information
_No response_
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thanks for reporting this. We're tracking this issue in #10547.
Thank you. The update Version 260204.1342 (531) has fixed it.
I am also hitting this on the macOS Desktop app in . During an app upgrade, Codex deleted git worktrees across multiple projects and erased uncommitted work in those worktrees. This is severe data loss, not just thread visibility. It happened immediately after upgrading. Please treat this as high severity; I can share repro details/logs if helpful.
Correction: affected version is macOS Desktop App Version 26.212.1823 (661). Upgrading deleted git worktrees across multiple projects and erased uncommitted work in those worktrees.
Just happened to me too, updating Codex instantly deleted a bunch of worktrees that I hadn't pushed to remote. Brutal. In case it's useful to anyone, I was able to recover individual files that I cared about via the codex logs if codex touched/catted them: grep -R -n -F "filename" ~/.codex/sessions ~/.codex/archived_sessions 2>/dev/null
Same for me, cli and app up-to-date. Now sure it's a duplicate of issue in https://github.com/openai/codex/issues/10547 @etraut-openai
Environment:
Steps: