Project sidebar loses existing chat threads after restart despite sessions remaining in session_index.jsonl
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by comparing the sessions listed in C:\Users\Owner.codex\session_index.jsonl with the project threads shown in the Codex sidebar. Investigate how project indexing handles completed sessions and restart, then verify that all existing threads reappear without deleting local session data.
Written by the indexing model from the issue text.
Description
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.
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
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·