Assistant replies missing from desktop history after using voice mode on mobile #43267

Activity

1. lgollut

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Sep 6, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   sessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving

   on Sep 6, 2026
3. github-actions commented on Sep 6, 2026

   

   github-actionsbot

   on Sep 6, 2026 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected. Please review them and close your issue if it is a duplicate.

   • Final response is incorrectly placed inside the Thinking/“Worked for” section, leaving no visible output #41948

   Powered by Codex Action
4. lgollut commented on Sep 6, 2026

   

   lgollut

   on Sep 6, 2026

   Author

   More actions

   I reviewed #41948. I’m seeing the same desktop symptom, with additional cross-device observations:

   • The task was started on Codex desktop, then continued on mobile, where I used voice mode.
   • When I returned to desktop, assistant replies were missing, leaving “Worked for…” indicators. Those same replies were visible on mobile.
   • Restarting desktop immediately restored display of new replies.
   • Replies missing before the restart remain absent from desktop history but visible on mobile.

   I haven’t confirmed whether mobile voice mode caused this, or whether the missing replies are inside the Thinking section.
5. globaswu commented on Sep 8, 2026

   

   globaswu

   on Sep 8, 2026

   More actions

   Windows follow-up: missing text replies after exiting realtime voice

   I observed the same visible symptom on Windows on September 8, 2026. It may be related to this issue; a common underlying cause has not been established.

   Environment

   • Windows 11 Pro, version 10.0.26200, build 26200.
   • Windows package: OpenAI.Codex 26.901.6511.0, checked both before and after restarting the app.
   • User-selected model/reasoning setting: GPT-6 Astra / Ultra; no comparison with other models was performed.
   • An existing long-running local task with subagents. This has not been reproduced in a fresh task or profile.

   Observed incident sequence

   1. Used realtime voice in an existing task, then exited voice and continued with ordinary text messages.
   2. A subsequent turn completed, but the PC conversation showed the user message and only "Worked for 30s", without the normal assistant-answer bubble.
   3. Asking for the result again did not immediately resolve the missing-answer display.
   4. A read-only check found the complete assistant reply in the local session transcript, followed by a completion event. This was not simply a failure to generate an answer.
   5. Restarted Codex and requested a fresh plain-text reply. That new reply was visible again, which the user confirmed.

   Recovery of the earlier missing bubbles was not verified. Whether the answers were available inside an expanded activity/thinking section was also not checked. Repeatability is unknown.

   Sanitized diagnostic observations

   • The affected turn was recorded as completed with no reported turn error; the recorded duration was approximately 30 seconds.
   • The transcript contained the full assistant message with phase final_answer, followed by task_complete containing the reply.
   • Desktop logs recorded the affected turn being handled by a hidden avatarOverlay, while the visible primary renderer had the stream role follower. Whether that routing was abnormal is unverified.
   • ResizeObserver errors occurred shortly after completion. This is correlation only; they have not been shown to cause the missing reply.
   • Subsequent history/item-read requests completed successfully. Their success alone does not establish that the visible client rendered the returned messages.

   Expected behavior and hypothesis

   After leaving voice, subsequent text turns should display their assistant answers normally without requiring an app restart.

   A stale voice-session or window-routing state is a hypothesis worth investigating, not a confirmed diagnosis. The internal voice-active state was not inspected. The observation that a new reply became visible after restart does not establish that the underlying defect was permanently fixed.

   No work content, project identifiers or URLs, conversation/turn identifiers, screenshots containing work content, raw logs, or full transcripts are attached.
6. antoinecorbel7 commented on Sep 23, 2026

   

   antoinecorbel7

   on Sep 23, 2026 – with ChatGPT Codex Connector

   More actions

   Related macOS observation: the desktop task view can show a "Worked for..." summary without the assistant's completed answer after a voice session ends. In an inspected occurrence, the final answer was present in saved task history and the task was reported as completed, but the main conversation view remained stale.

   Restarting the desktop app temporarily restores normal behavior; the problem can return after another voice session. This was observed on 26.915.31945 and again after updating to 26.917.62051.

   Scope clarification: this observation is from ending voice in the desktop app, not an independent reproduction of the mobile-to-desktop sequence. Recovery of all previously missing answer bubbles has not been established. A shared underlying cause remains unconfirmed.
7. potto007 commented on Sep 30, 2026

   

   potto007

   on Sep 30, 2026

   Last edited by potto007

   More actions

   I hit this today on Windows, app version 26.928.1915.0.

   The voice session was on my phone, connected remotely to the existing desktop task. I also used the computer keyboard while that phone connection was active. The desktop showed my messages and "Worked for..." summaries but omitted the assistant replies. The replies were present in the saved task history. Switching away from the task and back did not restore them.

   Here is the recovery sequence that worked for me:

   1. Disconnect the phone app's remote connection.
   2. Start voice chat in the same task on the desktop.
   3. Say something and receive a response from the agent through desktop voice.

   After that exchange, the agent's output began appearing in the session again. I then stopped desktop voice and confirmed that ordinary text replies were visible too.

   This was one occurrence. I have not tested whether simply toggling desktop voice is enough, whether the spoken exchange is required, or whether simultaneous phone voice and desktop keyboard input is necessary to trigger the bug. I also have not checked whether every earlier missing reply reappeared.