[Windows][Mobile] Turns completed from Codex mobile are missing from the Desktop transcript

What version of the Codex App are you using?

Not captured at the time of the report. The reporter can add the value from About Codex if maintainers need it.

What subscription do you have?

Not specified.

What platform is your computer?

• Host: Codex Desktop on Windows
• Remote client: Codex in the ChatGPT mobile app
• Both surfaces were using the same active Codex conversation and connected host

What issue are you seeing?

A conversation was continued normally from Codex in the ChatGPT mobile app. The mobile turns completed successfully and generated files on the connected Windows host, but that segment of the conversation did not appear in the Codex Desktop transcript.

There is strong evidence that the missing turns actually ran:

• mt5/Indicators/Session90TrendPosition.mq5 was written at approximately 15:20
• tradingview/Session90TrendPosition.pine was written at approximately 15:53

The generated source files are complete and remain on the Windows host. However, when returning to Desktop, the mobile conversation segment that produced them was absent. Earlier and later Desktop-visible turns remained available.

Observed date and time:

• July 14, 2026
• Approximately 15:20–15:53
• Australia/Sydney time zone (UTC+10 on that date)

This may be either:

1. a missing live invalidation/refresh in the open Desktop renderer,
2. a mobile-to-desktop persistence/indexing failure, or
3. a divergent thread branch that is not surfaced in Desktop.

At the time of this report, it has not been established whether fully restarting Desktop causes the missing turns to reappear.

What steps can reproduce the bug?

1. Open an existing active conversation in Codex Desktop on Windows.
2. Open the same connected host and conversation through Codex in the ChatGPT mobile app.
3. Continue the conversation from mobile.
4. Ask Codex to create or modify files on the connected Windows host.
5. Confirm from mobile that the turns complete successfully.
6. Return to the already-open conversation in Codex Desktop.
7. Observe that the file changes exist on disk, but the corresponding mobile turns are absent from the Desktop transcript.

What is the expected behavior?

Turns completed from Codex mobile in the same active conversation should appear consistently in the Codex Desktop transcript. If Desktop cannot update live, it should provide a deterministic refresh/reload path and converge on the complete persisted thread.

What actually happened?

The remote task executed and persisted its file outputs, while the mobile-authored conversation segment was missing from the Windows Desktop transcript. This makes the conversation appear incomplete and removes the reasoning and instructions associated with the generated files.

Additional information

No private Codex logs, account data, absolute workspace paths, or raw conversation content are attached to this public report.

Related or adjacent reports:

• #21743 — Desktop open thread does not refresh after another app-server client appends a turn
• #11907 — cross-surface conversation refresh/sync gaps
• #21513 — session divergence between clients
• #22800 — Codex mobile thread visibility/state sync issue