So Codex said there was an update available. So I clicked on it and it restarted. Now all my projects are gone and all my chat threads. I’ve literally lost everything. Is this normal after an update? Anyway to get it all back?
Similar situations have been noted before, however sometimes the solution is a simple reverting back to an earlier version of Codex.
Below each topic on this forum are Related topics that are often of value.
Also consider searching the OpenAI GitHub Codex issues as some may have replies from OpenAI developers or other users that have found a solution or work around.
Thanks. I did try a search first and it turned up nothing. Perhaps my keywords were not right. Hard to know what to search for sometimes with issues like this. I did discover though that if I added the project folder back into Codex, my old threads appeared again. So hopefully it is all okay.
If you still do not have your missing data, look for directories named .codex as the default location for storing local information on a PC will have this in the path.
If you do find the directory or directories as some of these diretories are also local to a project, then make backup copies of them all just in case.
Also remember to clear the credentials from backup file(s).
Simple solution for me was to simply ask it to restore the missing chats. It scanned the sessions folder, found them in the JSONL files, checked the session database and found some were missing title/description metadata and the front-end refused to load them, so it generated those and restored them to the front-end. I had to move them from recent chats back into the project but it worked.
Welcome to the community, @wyt3dr4g0n, and thanks for sharing this solution. Restoring the missing title and description metadata could be a useful workaround for others whose chats are still present in the session files but not loading in the front end.
Appreciate @EricGT pointing out the similar reports as well. @rubasurex, are you still experiencing the issue, or did this approach help?
-Mark G.
@rubasurex, we followed up four days ago to check whether you’re still experiencing this issue, but we haven’t received a response.
Since there hasn’t been any further update, we’ll go ahead and close this case for now. We hope the issue has since been resolved.