[Windows App] Assistant replies stop appearing after voice-to-text session; terminating processes and relaunching restores visibility

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

Installed Windows package: OpenAI.Codex 26.915.4065.0, verified with Get-AppxPackage (not the About dialog).

What subscription do you have?

ChatGPT Pro.

What platform is your computer?

Windows 11 Pro, OS version 10.0.26200, build 26200.

What issue are you seeing?

During a long existing conversation, after a voice session ended and work continued by text, the user could send messages but could no longer see the assistant's new replies in the Windows app. Several follow-up messages and short assistant replies did not resolve the visible symptom.

The agent still received requests and executed tools. At the user's explicit request, it sent a Telegram notification through an existing remote-machine setup. The Telegram API confirmed successful delivery, and the user confirmed receipt. This establishes that agent execution remained functional while the user reported no visible replies in the desktop conversation.

What steps can reproduce the bug?

Observed sequence, not a deterministic minimal reproduction:

1. Use a long-running Codex Windows conversation with tool execution.
2. Start and end a voice session, then continue by typing in the same conversation.
3. Send follow-up messages. The agent responds and can execute tools, but new replies are not visible to the user.
4. Terminate Codex processes from Windows Task Manager and relaunch Codex.
5. The user confirmed that replies became visible again after this recovery.

The voice transition is context, not an established cause. Exact triggering action, token usage, and context utilization are unknown. Private conversation identifiers and project content are intentionally omitted.

What is the expected behavior?

New assistant replies should appear in the active conversation while work continues, including after switching from voice to text. Recovering message visibility should not require terminating the application's processes.

Additional information

Observed September 19, 2026. Recovery was confirmed by the user after terminating processes and restarting Codex; a normal close-and-reopen alone was not isolated as a separate successful recovery. No diagnosis of data loss or specific renderer/backend failure is claimed.

Possibly related: #44035 reports missing Windows conversation history while agent work continues. This report does not establish that its stale read_thread behavior or root cause applies here. No raw transcripts, credentials, or private project data are attached.

No files, tests, or entry points are named. Start by reproducing the reported Windows sequence: end a voice session in a long conversation, continue by text, and check whether replies remain visible without restarting the app. Done means assistant replies reliably appear after the transition and the recovery no longer requires terminating processes.