Desktop remote conversation shows only Worked for durations while persisted final responses display on mobile #53592

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

Desktop and mobile client versions have not yet been collected. Please do not interpret the remote server version as the desktop app version.

What subscription do you have?

Not collected.

What platform is your computer?

The affected desktop client's OS has not yet been collected. Both the desktop and mobile clients connect to the same remote Linux server (called XP by the reporter).

What issue are you seeing?

For the same remote conversation, the desktop client shows several completed turns with only a Worked for ... duration and no assistant response body. The reporter states that the corresponding responses display normally on mobile.

The screenshot supplied by the reporter shows, in sequence:

• A user request followed by Worked for 2m 21s and no response/error text.
• A follow-up followed by Worked for 5m 16s and no response text.
• A question about download speed followed by Worked for 47s and no response text.
• Another short user message followed by Worked for 24s and no response text.
• A Voice ended divider.
• A later user message followed by a normally visible assistant response.

The conversation records were inspected through read_thread. The follow-up, download-speed question, and short message all have status: completed, no error, and nonempty agentMessage items with phase: final_answer. For example, the download-speed response contains a Markdown table, while another missing response is plain text. Thus this affects both formatted and plain responses.

The first turn is different: it failed with Selected model is at capacity. Please try a different model. and has no final answer. Its screenshot position also appears to show only the duration. The confirmed missing-response cases are the subsequent completed turns.

What steps can reproduce the bug?

Observed sequence (a deterministic reproduction has not yet been established):

1. Connect desktop and mobile clients to the same remote Linux server.
2. Open the same conversation on both clients.
3. Complete several turns around a voice-session transition; the screenshot contains a Voice ended marker.
4. Compare the completed turns: desktop displays duration only, while mobile reportedly displays the response bodies.

Observed on 2026-10-13.
Thread ID: 01a13011-a2ff-71d1-884a-c0e45cba1346
Confirmed completed turns with missing desktop response bodies:

• 01a133e4-7d32-7033-8806-0a15c54292a6
• 01a133ed-fdbd-7970-8730-17b9cec49e1e
• 01a13404-9656-7c30-8129-1710546acc52
  Token/context-window usage was not collected.

What is the expected behavior?

Both clients should display the persisted final assistant responses for completed turns. Failed turns should display their error rather than appearing as silent completed work.

Additional information

Possible desktop rendering/synchronization issue; the root cause is unconfirmed. The voice-session marker is an observation, not proof that voice caused the issue.
The desktop screenshot has been inspected, but is not attached to this public issue. The complete conversation and raw logs have not been published. The text above describes the relevant UI state with unrelated conversation content omitted.