Project sidebar loses existing chat threads after restart despite sessions remaining in session_index.jsonl
What version of the Codex App are you using (From “About Codex” dialog)?
26.707.72221
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Windows 10 Pro x64
What issue are you seeing?
I believe this is a project/thread indexing bug rather than data loss.
Behavior observed:
I originally had five AI Broadcast Studio project threads.
One completed thread disappeared after finishing successfully.
After restarting the Codex desktop app, two additional project threads disappeared from the sidebar.
The project now shows only two threads.
However, the underlying data still exists.
I inspected:
C:\Users\Owner\.codex\session_index.jsonl
The missing sessions are still present in the session index, including:
Review SENB Daily Brief workflow
Build AI Broadcast Studio
Add logical workspace mapping
Refactor production run workflow
Add companion bridge
Update master documentation
Build executive producer workspace
Only two threads appear in the Codex project sidebar despite all sessions still existing locally.
Additional observations:
Archived Tasks is empty.
Restarting Codex does not restore the missing threads.
Updating to the latest Codex version did not resolve the problem.
The issue appears to affect project indexing only; it does not appear that the underlying sessions were deleted.
I also experienced one completed task showing a red warning icon before disappearing.
It would be helpful if there were a way to rebuild the project thread index without deleting local data.
<img width="1366" height="768" alt="Image" src="https://github.com/user-attachments/assets/63ef4905-663e-443a-90ba-b6473209c2f8" />
<img width="1366" height="768" alt="Image" src="https://github.com/user-attachments/assets/bf43e4d6-2bd1-4fe4-91e1-52394e503351" />
What steps can reproduce the bug?
Feedback ID: no-active-thread-019f6c06-1c77-75a1-9821-932a5e219223
What is the expected behavior?
_No response_
Additional information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗