Codex Desktop: phone-created thread opens from Search but is missing from sidebar
Summary
A Codex thread that was originally started from Codex on phone syncs to Codex Desktop on Windows and can be opened through Search, but it does not appear in the normal left sidebar/project thread list. The user has to search for the thread every time to reopen it.
Environment
- Product: Codex Desktop
- Desktop OS: Windows 10 Pro, WindowsVersion 2009, OS build 26200
- The thread was originally started from Codex on phone, then opened on desktop through Search.
- The thread is usable once opened from Search.
- The issue is visible while viewing the desktop left sidebar/project thread list.
Steps to reproduce
- Start a Codex thread from Codex on phone.
- Continue work in the thread long enough that it has a title and normal thread content.
- Open Codex Desktop on Windows.
- Use Search to locate the thread by title/content.
- Open the thread from Search.
- Look for the same thread in the left sidebar/project thread list.
Expected behavior
The opened/synced thread should appear in the normal left sidebar/recent thread list, or there should be a clear way to add, move, or pin the phone-started thread into the desktop project/thread list.
Actual behavior
The thread opens from Search and is usable, but it does not appear in the visible left sidebar/project thread list. Unless the user searches for it every time, it is difficult to locate again.
Evidence gathered
- A screenshot shows the thread open on Codex Desktop while the visible left sidebar/project thread list does not include the open thread.
- Local Codex session data exists for the thread on the desktop machine, so this does not appear to be missing local session content.
- This looks like a desktop sidebar/project association or indexing issue for a phone-started synced thread.
Privacy note
A screenshot exists but is not attached because it contains account and local workspace details. It can be provided through a private support channel if needed.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗