Existing desktop thread can be opened by ID but is missing from sidebar and not returned by thread list/search
Resolved 💬 2 comments Opened Jul 6, 2026 by Northern-Summer Closed Jul 6, 2026
What version of the Codex App are you using?
26.623.13972.0
What platform is your computer?
Windows
What issue are you seeing?
A desktop thread still exists and can be opened directly by thread ID, but it does not appear in the left sidebar and is not returned by thread listing or thread search.
This looks like a split between:
- direct thread-read path: works
- sidebar/list/search/thread-management path: fails
Steps to reproduce
- Have a desktop thread that previously existed normally.
- Observe that it disappears from the left sidebar.
- Try listing or searching for it from the app thread list.
- Try opening or reading it directly by thread ID.
Expected behavior
If a thread still exists locally and is readable, it should:
- appear in the left sidebar
- be returned by thread listing
- be returned by thread search
- be manageable by normal thread operations
Actual behavior
- Direct read or open by thread ID still works.
- The thread does not appear in the left sidebar.
- Thread search by exact title returns nothing.
- Thread search by exact thread ID returns nothing.
- Thread management operations such as rename or archive fail as if the thread does not exist.
Additional technical clue
The missing thread appears to have abnormal summary or title metadata:
- title and preview are very long and look like body content or a pasted first-user-message summary, rather than a short thread title
- this suggests the thread may still exist in storage, but the sidebar or list index layer may be dropping or failing to register malformed metadata rows
Why this seems important
This is not just sorting or pagination:
- the thread can still be opened directly
- but enumeration, search, and management paths act like it is gone
That suggests a bug in thread indexing, registration, or metadata validation for sidebar-visible threads.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗