Thread disappeared that was inside a Project and on a Worktree

[kaleidoKurt]

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

Version 260205.1301 (554)

What subscription do you have?

Plus

What issue are you seeing?

I was working on a Thread within a Project on a Worktree and after I restarted the Codex app, the Thread had completely disappeared.

The Worktree still exists, but the thread is gone.

What steps can reproduce the bug?

I've restarted the Codex App multiple times to see if the thread will reappear or other threads will disappear. No luck so far on either fronts.

What is the expected behavior?

No response

Additional information

No response

[etraut-openai]

Please make sure you're on the latest version of the app. Let us know if you're still seeing this.

[kaleidoKurt]

@etraut-openai I am. Checked for updates:

"You're up to date! Codex 260205.1301 is currently the newest version available."

[paobaodao]

Exact same issue. Lost important work because of this bug. Thread was partially deleted. It appears that work done within last several hours was not "committed" and restart for update deleted that part of the thread.

[kaiengelhardt]

Just today, I lost all my threads suddenly. I just updated to the latest version.

[kaiengelhardt]

I found some archived threads. Unarchiving them removed them from the list of archived threads, but they are not visible at all in the project sidebar. So now they are effectively gone.

[tillkolter]

@kaiengelhardt
I had the same problem with archived thread and I managed to get them back :)

I think the problem relates to the original worktrees being cleaned up when archiving. Unfortunately unarchiving doesn't seem to recreate that worktree, it just moves the session from ~/.codex/archived_sessions/** into the ~/.codex/sessions/<yyyy>/<mm>/<dd>/folder.

Here is my recipe to restore succesfully:

• ask Codex to dig into the recent ~/.codex/sessions (or archived_sessions), give it some of the keyword you have been working on, I am sure it will uncover it
• ask to restore the original worktree (the reference is somewhere in that JSON file)
• restart

(It goes without saying: you don't need codex to do it, just have to do all the worktree restoring youself, the gist is: things are not lost, it's just JSON files needing to be "hydrated" into the expected git folder structure.)

Good luck and Happy coding.

[devinbarry]

I am also hitting this on the macOS Desktop app in Version 26.212.1823 (661). 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.

[etraut-openai]

@devinbarry, to clarify, did you see threads disappear or worktrees? This issue is about threads disappearing. If you're seeing a different behavior, please open a separate bug report.

[devinbarry]

@etraut-openai Confirming: I lost both. The app upgrade deleted git worktrees across multiple projects, and the threads associated with those deleted worktrees were also gone/inaccessible afterward. This included uncommitted work in those worktrees.

[cantonalex]

Same here. Only have one from 1w ago now and i had tons.. 26.217.1959. yeesh just lost a lot of work

[ciriousjoker]

The way to get these back for me seems to be to sort chronologically and pin them to the top so I can go back to project-grouped.

Still really annoying.
Version 26.217.1959 (669)

[SyahmiRafsan]

@kaiengelhardt I had the same problem with archived thread and I managed to get them back :)

I think the problem relates to the original worktrees being cleaned up when archiving. Unfortunately unarchiving doesn't seem to recreate that worktree, it just moves the session from ~/.codex/archived_sessions/** into the ~/.codex/sessions/<yyyy>/<mm>/<dd>/folder.

Here is my recipe to restore succesfully:

• ask Codex to dig into the recent ~/.codex/sessions (or archived_sessions), give it some of the keyword you have been working on, I am sure it will uncover it
• ask to restore the original worktree (the reference is somewhere in that JSON file)
• restart

(It goes without saying: you don't need codex to do it, just have to do all the worktree restoring youself, the gist is: things are not lost, it's just JSON files needing to be "hydrated" into the expected git folder structure.)

Good luck and Happy coding.

Based on the paths from above, Codex is able to get the missing threads for me.

Just tell Codex to check the local + UI thread index per repo.

Edited: it still unable to show the threads on the UI sidebar....