macS app lost "Archived" threads permanently when trying to "Unarchive"

Open 💬 3 comments Opened Feb 18, 2026 by coldpointblue

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.217.1959 (669)

What subscription do you have?

Personal

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

macOS app lost "Archived" threads permanently when trying to "Unarchive", gone from UI, in no project anymore, because folder was moved while Codex not running, when I came in and chose to "Unarchive" content in that conversation from the Settings button bottom left in the app "Settings:Archived Threads" menu item in the menu, pressing the 'Unarchive' button removed the thread from the UI there but clicking go there, simply disappeared the notice and in the normal threads UI in the home screen there was no project for that, nor warning, no indication what happened to archive of threads.
It is no longer in the Archived threads UI, no longer in the home UI, so gone from use.

What steps can reproduce the bug?

Archive thread.
Quit Codex.
Move folder or duplicate it, delete it then rename the duplicate with same name.
Launch Codex.
Settings button "Settings:Archived threads" item. You see Archived threads in UI to the right.
Press "Unarchive" button from thread from that file. Thread disappears. Notice on top disappears after that.
Go home with "Back to app" top left.
You don't see the project (it was not there to begin with, there was no warning that Archive is gone.
Archive has no project, not in UI.

What is the expected behavior?

Correct test:
would be to warn that the folder is gone, ask to find again or at least see a notice somewhere that project is not found and KEEP THE ARCHIVED THREAD IN THE UI. Since the folder is renamed or gone, Codex cannot find it. Don't disappear the archive from UI.

Additional information

There should be some warning in the app about folder not found. Archive thread should remain in UI instead of disappearing.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗