Codex Desktop history missing from sidebar after update, while CLI and deep links can access sessions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The payload points at ~/.codex/state_5.sqlite, where the threads table has has_user_event=0 for the affected rows, and at the rollout JSONL files under ~/.codex/sessions/, which contain the user messages. Start by checking which code writes has_user_event and how the Desktop sidebar filters threads, then compare against what codex resume --all in CLI 0.161.0 lists. Done means the affected threads reappear in the sidebar without manual database edits, and the fix is confirmed on a database where has_user_event is 0.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.1002.52244
What subscription do you have?
Pro
What platform is your computer?
Darwin 25.6.0 arm64 arm
What issue are you seeing?
After updating Codex Desktop on macOS to version 26.1002.52244 (Oct 7, 2026), several existing conversations disappeared from the Desktop sidebar, although they remain accessible through Codex CLI 0.161.0 using codex resume --all and can also be opened directly via codex://threads/<session_id>. I inspected ~/.codex/state_5.sqlite and found 8 regular user threads, all with source=vscode, archived=0, valid rollout JSONL files, existing working directories, and non-empty preview and first_user_message fields. However, all 8 threads have has_user_event=0, despite their JSONL files containing between 5 and 192 actual user messages. I have already tried restarting Codex, rebuilding the Desktop UI cache, reopening the original project directories, and updating has_user_event=1 for one affected thread after creating a backup. None of these restored the missing conversations to the sidebar. SQLite integrity checks return ok. I also previously resumed some sessions using the CLI and terminated a lingering Codex process, although I cannot confirm whether this is related. Expected behavior: All existing, non-archived user conversations should remain visible in the Desktop history/sidebar after updates. Actual behavior: Some conversations are hidden from the sidebar despite being readable through CLI and direct deep links. Could you investigate whether this is caused by a Desktop thread catalog synchronization, source filtering, or session indexing issue, and provide a supported way to rebuild the conversation list without losing history?
What steps can reproduce the bug?
Steps to Reproduce
- Use Codex Desktop on macOS to create several conversations across different projects, including long-running conversations initiated through the VS Code integration.
- Confirm that the conversations contain user messages and assistant responses and are initially accessible.
- Update Codex Desktop to version 26.1002.52244 (Oct 7, 2026) and restart the application.
- Open the original projects in Codex Desktop and check the conversation sidebar. Some previously existing conversations are missing.
- Open Terminal and run
codex resume --allusing Codex CLI 0.161.0. The missing conversations are still listed and can be resumed successfully. - Open an affected conversation directly using
codex://threads/<thread_id>. The conversation opens correctly in Codex Desktop, but it still does not appear in the normal sidebar history. - Restart Codex Desktop and rebuild its UI cache. The missing conversations remain absent.
What is the expected behavior?
Expected behavior: All existing, non-archived conversations should remain visible in the Codex Desktop sidebar after an update.
Actual behavior: Some conversations disappear from the sidebar, even though they remain accessible through the CLI and direct thread links.
Reproducibility: Observed consistently on my existing installation after the update. I have not confirmed whether the issue reproduces on a clean installation.
Additional information
Additional Findings
- The affected conversations exist in
~/.codex/sessions/and are recorded instate_5.sqlite. - The regular user threads have
archived=0,source=vscode, and valid, non-emptypreviewandfirst_user_messagefields. - All 8 regular user threads have
has_user_event=0, despite their JSONL files containing actual user messages. - Manually setting
has_user_event=1for one affected thread did not resolve the issue. - SQLite integrity checks return
ok. - I previously used
codex resumeand force-terminated a lingering CLI process. I am unsure whether this contributed to the issue.
- Dominant language
- Rust
- Stars
- 130k
- Forks
- 20.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 998
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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
-
bug CLI TUI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
app-server documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openai/codex#55328 · 1 comment ·
Maintainers usually reply within 1 day
-
bug CLI
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openai/codex#55122 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
peteonrails/voxtype#909 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
alchemyplatform/rundler#1358 ·
Maintainers usually reply within 3 days
-
[BUG] VA-API HEVC: out-of-range cu_qp_delta (measured -130..+56) produces a corrupted bitstreamOpen
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
selkies-project/pixelflux#52 · 4 comments ·
Maintainers usually reply within 1 day
-
llm translation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BerriAI/litellm#47884 · 1 comment ·
Maintainers usually reply within 1 day
-
area:testing bug good first issue platform:windows priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day