Existing Codex Desktop thread is missing from Remote on Android while new threads sync correctly

What version of the Codex App are you using (From “About Codex” dialog)?

26.909.11814

What subscription do you have?

ChatGPT Pro (upgraded from Plus around the time the issue first appeared)

What platform is your computer?

Microsoft Windows NT 10.0.19045.0

What issue are you seeing?

An existing, actively used Codex Desktop thread is fully available and usable on the original Windows host, but it is completely missing from ChatGPT Android > Remote.

The affected thread:

• does not appear in Remote Recent Threads
• cannot be found through Remote search
• remains missing even after continued activity on the Desktop thread
• continues to work normally on the original Windows host

A newly created control thread in the exact same ChatGPT account, workspace, Windows host, Codex project, and local workspace appears correctly in Android Remote.

This indicates that Remote connectivity itself is working, but the existing thread is not being discovered/indexed by Remote.

There is also an apparent project-name inconsistency:

Desktop:
Museum Rescue_V2

Android Remote shows separate entries:
MuseumRescue
Museum-Rescue-V2

The affected existing thread does not appear under either Remote project entry.

Environment:

• Codex Desktop: 26.909.11814
• Desktop OS: Windows
• ChatGPT Android: 1.2026.251 (11)
• Subscription: ChatGPT Pro
• Issue reproduces on both Wi-Fi and cellular data
• Approximate first occurrence: September 14, 2026 (KST / UTC+9)

The issue became noticeable around the time I upgraded from ChatGPT Plus to Pro. I cannot confirm that the subscription change caused the issue; the timing may be coincidental.

I have already submitted in-app feedback from the affected thread with diagnostic logs/session context shared with OpenAI Support.

For privacy reasons, I am not posting the session/thread identifiers publicly in this issue, but they have already been provided to OpenAI Support and can be shared privately with an OpenAI maintainer if required.

What steps can reproduce the bug?

1. On Codex Desktop for Windows, open an existing long-running development thread in a local project.

2. Confirm that the existing thread is still fully usable on the Windows host.

3. Connect an Android phone to the Windows host using ChatGPT Remote.

4. Open Remote on Android.

5. Check Recent Threads and search for the existing Desktop thread.

6. Observe that the existing thread is not present and cannot be found through Remote search.

7. In the same Codex Desktop project and local workspace, create a new control thread.

8. Refresh Remote on Android.

9. Observe that the newly created control thread appears correctly in Remote, while the existing thread remains missing.

Additional troubleshooting already performed:

• refreshed Mobile Remote
• cleared Android app cache
• signed out and back in
• restarted Codex
• checked for Codex Desktop updates
• re-paired the Android phone using a fresh QR code via Settings → Connections → Control this Mac or PC
• tested on both Wi-Fi and cellular data
• searched Remote for the affected thread
• continued working in the affected Desktop thread
• verified that the affected thread exists in the local Codex database
• verified that the affected thread is not archived
• verified its local project assignment
• compared its local metadata with the Remote-visible control thread
• submitted in-app feedback from the affected thread with diagnostic logs included

The problem remains unchanged after all of these steps.

What is the expected behavior?

An existing active Codex Desktop thread belonging to the connected Windows host and project should be discoverable and resumable through ChatGPT Remote on Android.

Existing threads and newly created threads in the same project/workspace should be exposed consistently through Remote.

Re-pairing the same host/device should not result in existing active threads being omitted from Remote discovery or search.

Additional information

This issue is materially disrupting and delaying an active game development project.

The affected thread is my main ongoing development session and contains substantial accumulated context, including:

• implementation history
• architecture decisions
• game design decisions
• project constraints
• test/build history
• unfinished development work
• current implementation state

Because this thread is unavailable through Remote, I cannot reliably continue the same development context across devices.

I have already spent significant development time diagnosing and working around this issue instead of progressing the project.

Creating a new thread is not an equivalent workaround because manually transferring and revalidating the accumulated context introduces additional development cost and risks losing important technical/design decisions or creating inconsistencies.

A newly created control thread in the same project/workspace appears normally in Android Remote, which is why this appears to be an existing-thread discovery/indexing issue rather than a general connectivity problem.

I have already submitted in-app feedback from the affected chat with diagnostic logs/session context included, and the feedback/session identifier has been shared directly with OpenAI Support.

I can provide the exact affected/control thread identifiers and feedback session identifier privately to an OpenAI maintainer if needed.

Please investigate this as a Codex Remote thread discovery/indexing bug affecting existing Desktop threads.

Start by comparing the affected thread and the Remote-visible control thread in the local Codex database, including their project assignment and metadata. Trace how Remote Recent Threads and search discover existing Windows Desktop threads, using the supplied diagnostic logs and private thread identifiers if needed. Done means the active existing thread appears and can be resumed in Android Remote consistently with the new control thread.