Repository navigation
Remote conversation is visible on the host machine but never syncs to ChatGPT Web or Android #36244
Description
What issue are you seeing?
One specific Remote Codex conversation never appears on any other device, even though:
Remote Host is online.
Other newly created conversations sync correctly.
The problematic conversation continues to work normally on the original machine.
This appears to be a conversation-specific synchronization issue, not an account or device issue.
Environment
Codex Desktop: Windows
Remote Host: MFC-YH
ChatGPT Android App: latest version
ChatGPT Mobile Web: same account
OpenAI account: same account on all devices
Expected behavior
A Remote conversation created on the desktop should appear in:
Android ChatGPT Remote
ChatGPT Web
Other devices logged into the same account
Actual behavior
One conversation (ASRGroq 設計規格) never appears anywhere except on the original desktop.
However:
It continues to function normally on the desktop.
New messages can still be exchanged.
Newly created Remote conversations sync normally.
Reproduction
Create/use Remote conversation ASRGroq 設計規格.
Continue working in that conversation.
Open ChatGPT Android Remote.
Conversation is missing.
Search by title.
No results.
Open ChatGPT Mobile Web.
Conversation is still missing.
Verification performed
Confirmed:
✅ Same OpenAI account
✅ Same Remote Host
✅ Host is online
✅ Android cache cleared
✅ Android app restarted
✅ Mobile browser tested
✅ Conversation renamed
✅ New messages added (sync test)
✅ Waited for synchronization
No change.
Important observation
Creating a new Remote conversation immediately syncs across all devices.
For example:
New conversation: 檢查測試狀態
Appears on Android within minutes.
Only the existing conversation:
ASRGroq 設計規格
never synchronizes.
This strongly suggests the problem is tied to one specific Conversation ID, rather than the account, Remote Host, or synchronization service in general.
Additional observations
The affected conversation remains fully usable on the original desktop.
It is not archived.
Renaming the conversation does not trigger synchronization.
Sending new messages (sync test) also does not trigger synchronization.
Other Remote conversations continue to synchronize normally.
Suspected cause
Possible server-side metadata/index corruption for a single Remote Conversation.
The conversation appears to exist locally and remain usable, but is never indexed for cross-device synchronization.
Impact
The conversation cannot be accessed from:
Android ChatGPT
ChatGPT Web
Any other device
Only the original desktop can continue using it.
What steps can reproduce the bug?
Create/use Remote conversation ASRGroq 設計規格.
Continue working in that conversation.
Open ChatGPT Android Remote.
Conversation is missing.
Search by title.
No results.
Open ChatGPT Mobile Web.
Conversation is still missing.
What is the expected behavior?
No response
Additional information
No response
Activity
github-actions commentedon Jul 31, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
YihongTools commentedon Jul 31, 2026
I reviewed the suggested duplicates.
#35800 appears highly related and may share the same underlying thread registration or Remote enumeration failure.
However, my case has an additional distinguishing detail:
on the same Windows host and project, a newly created test conversation synchronized successfully, while one specific existing conversation remained permanently absent from both Web and Android.
#36164 appears broader because it affects multiple Work-related object types.
#35233 does not contain enough diagnostic detail to confirm whether it is the same issue.
YihongTools commentedon Aug 3, 2026
Additional related reports have now appeared:
Together with #35800 and this Windows case, this may indicate a cross-platform desktop conversation registration or server-side enumeration issue rather than an Android- or Windows-specific client problem.
YihongTools commentedon Aug 14, 2026
Another related report, #37385, may provide an important additional clue.
It describes the reverse direction of the synchronization failure: Android Remote-created conversations successfully execute work on the Mac host, but those conversations never appear in the desktop app history.
In my case (#36244), the affected conversation exists and remains usable on the Windows desktop host, but never appears in Web or Android Remote.
So the two cases fail in opposite directions:
Notably, #37385 reports evidence that the Remote-created conversation was not added to the desktop-visible
~/.codex/session_index.jsonl.Together with #35800, #36496, and #36623, this further suggests a cross-client conversation persistence/registration/indexing consistency issue rather than a platform-specific UI or cache problem.