[Windows/Mobile Remote Voice] Voice session abruptly drops to text and loses context after reconnect

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

Not captured.

What subscription do you have?

Not captured.

What platform is your computer?

Windows laptop. The mobile OS and app version were not captured.

What issue are you seeing?

During a live Codex Remote Voice conversation from a mobile device connected to a Windows laptop running Codex, the session initially works normally. After some time, Voice abruptly disconnects without the user ending it and the mobile experience falls back to text.

The user must manually re-enable Voice. After Voice is restarted, the assistant no longer appears to retain the context of the spoken conversation that occurred before the drop, so the conversation cannot continue seamlessly.

This appears to be an intermittent synchronization or session-handoff problem between the mobile Voice client and the laptop-hosted Codex thread.

What steps can reproduce the bug?

1. Run Codex on a Windows laptop.
2. Connect to that Codex session from a mobile device using Remote Voice.
3. Continue a spoken conversation normally for some time.
4. Observe that Voice can abruptly disconnect and the client returns to text mode, without the user explicitly ending Voice.
5. Re-enable Voice in the same conversation.
6. Continue speaking and observe that the assistant may not retain or recover the conversational context from before the disconnect.

Reproducibility: intermittent/recurring; no fixed duration before the drop has been identified.

Observed: September 14, 2026.

What is the expected behavior?

• Voice should remain active until the user explicitly ends it or a clear recoverable connection error occurs.
• If the transport disconnects, the client should reconnect or resume the same Voice session.
• Restarting Voice in the same thread should preserve the prior transcript and conversational context.
• Mobile and laptop thread state should remain synchronized across the interruption.

Actual behavior

• Voice unexpectedly stops.
• The interface falls back to text.
• The user must manually restart Voice.
• After restart, the assistant behaves as though part or all of the prior spoken context is unavailable.

Additional information

Possibly related reports:

• #45223 — Voice conversation sync and incomplete history in the new desktop app
• #43267 — Assistant replies missing from desktop history after using Voice on mobile

This report is narrower: it concerns an active Remote Voice session collapsing to text and losing continuity when Voice is re-enabled. No logs or private transcript content are attached.

Start by reproducing the intermittent Remote Voice flow across a mobile device and Windows laptop, following the six steps in the report. The payload names no files or tests; investigate the session handoff and transcript synchronization around the Voice-to-text fallback. Done means Voice remains active or recovers, and restarting it preserves the prior transcript and context.