Codex Remote omits desktop-created threads after latest Codex Desktop update

Summary

After the most recent Codex Desktop update, Codex Remote stopped displaying
some active, top-level threads created locally in the desktop application.

The visibility pattern is:

• Threads created before the desktop update remain visible in Remote.
• Threads created from Remote remain visible.
• Three consecutive top-level threads created locally after the desktop update

are absent from Remote.

Remote skips the affected threads and displays “No more threads,” even though
the sessions remain available locally.

Removing and reestablishing the Remote connection did not resolve the issue.

Environment

• Host operating system: Windows
• Affected desktop version: Codex Desktop 0.146.0-alpha.3.1
• Older visible threads include sessions created using 0.145.0-alpha.30
• Remote client: ChatGPT mobile app
• Remote connection status: Connected
• Project type: Local project

Identifying host, account, project, and session details have been omitted from
this public report. They can be provided privately to OpenAI Support if needed.

Observed visibility boundary

1. Threads created before the latest Codex Desktop update remain visible.
2. Threads created through the Remote client remain visible.
3. Three consecutive top-level threads created locally after the desktop update

do not appear in Remote.

1. Older and newer visible threads appear around the missing entries.
2. Remote reaches the end of its list and displays “No more threads.”

This suggests the problem may affect the registration, synchronization, or
enumeration of desktop-created threads after the update rather than Remote
connectivity or project selection generally.

Local verification

All three missing threads are:

• Top-level, user-created threads rather than sub-agent sessions
• Active and not archived
• Associated with the same local project as the visible threads
• Present in the local .codex/sessions directory
• Present in .codex/session_index.jsonl
• Readable locally, with their transcripts intact

The affected session metadata includes:

• thread_source: user
• source: vscode
• originator: Codex Desktop
• history_mode: legacy

Visible older sessions also use history_mode: legacy, so that field alone
does not explain the difference.

Exact session identifiers, titles, paths, and transcripts are intentionally
omitted from this public report. They can be provided privately to OpenAI
Support.

Steps to reproduce

1. Update Codex Desktop to the latest available version.
2. Open an existing local project.
3. Create a new top-level thread locally in Codex Desktop.
4. Connect to the same host and project using Codex Remote.
5. Review or search the Remote thread list.
6. Observe that locally created post-update threads may be absent.
7. Create another thread through Remote.
8. Observe that the Remote-created thread remains visible.
9. Confirm that threads created before the desktop update remain visible.
10. Remove and reestablish the Remote connection.
11. Observe that the missing locally created threads remain absent.

Expected result

All active top-level threads associated with the selected local project should
appear in Remote, regardless of whether they were created locally or through
Remote.

Actual result

Three consecutive active, locally created threads from after the latest
desktop update are omitted.

Pre-update threads and Remote-created threads remain visible. Remote reaches
the end of the displayed list and reports “No more threads.”

Troubleshooting already attempted

• Confirmed that Remote is connected
• Confirmed that the correct host and local project are selected
• Removed and reestablished the Remote connection
• Confirmed that the affected sessions are not archived
• Confirmed that the local transcript files exist and are readable
• Confirmed that the sessions appear in the local session index
• Confirmed that the affected sessions are top-level user threads
• Confirmed that older threads remain visible
• Confirmed that Remote-created threads remain visible

Privacy and diagnostic information

I have not attached the original screenshot because it contains identifying
project information.

I have also omitted session IDs, thread titles, host names, usernames,
filesystem paths, repository details, and transcript contents from this public
report.

I can provide the exact affected session IDs, relevant metadata, and a redacted
screenshot privately to OpenAI Support or an authorized maintainer.