macOS: final task answer missing after ending voice during Thinking, despite completion notification #45002

Activity

1. github-actions

   added

   bugSomething isn't workingSomething isn't working

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

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

   on Sep 12, 2026
2. github-actions commented on Sep 12, 2026

   

   github-actionsBot

   on Sep 12, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Voice exit leaves hidden overlay owning the thread; primary UI remains thinking #44645

   Powered by Codex Action
3. tomherman commented on Sep 16, 2026

   

   tomherman

   on Sep 16, 2026

   More actions

   I've had the same happen to me twice over a few weeks and different ChatGPT versions, but on Windows.
   #45861
4. antoinecorbel7 commented on Sep 23, 2026

   

   antoinecorbel7

   on Sep 23, 2026 – with ChatGPT Codex Connector

   More actions

   Additional macOS observation closely matching the missing-answer behavior:

   • After ending voice, the main task view can remain stale, showing a running indicator/Stop control or a "Worked for..." summary without the completed answer.
   • In an inspected occurrence, the saved task history contained the final answer and completion event, and the task was reported as idle/completed, while the visible conversation did not show the answer.
   • Fully quitting and reopening the app temporarily restores normal behavior, but the problem can recur after using and ending voice again.
   • The same pattern was observed on desktop version 26.915.31945 and again after updating to 26.917.62051.

   This supports the reported mismatch between completed work and the visible task state after voice ends. It does not establish the underlying cause or a permanent workaround.
5. mimeeq-neal commented on Oct 7, 2026

   

   mimeeq-neal

   on Oct 7, 2026

   More actions

   Additional user report as of 7 October 2026: ending a voice call while the underlying agent is still working can leave the normal written progress/result/final summary missing from the conversation, even though the work continues and may finish successfully. I then have to ask whether the work completed and what happened.

   This matches the end-of-call symptom described here. I also report experiencing it on mobile; that mobile behavior has not been independently reproduced, and the mobile version/platform details are not established.

   Current desktop environment checked read-only: Codex bundle version 26.930.61225, build 13232; macOS 26.6.2, Apple Silicon arm64. This establishes the currently installed environment, not the version of every previous occurrence. No fresh reproduction was performed for this comment.

   Minimal user-reported sequence:

   1. Start voice in a Codex task and request work that takes time.
   2. End the voice call while the underlying agent is still working.
   3. Return to the conversation after the work completes.
   4. The ordinary written result/final summary is absent or suppressed, requiring a follow-up question.

   Expected: when work continues after voice ends, the conversation should retain or backfill ordinary progress and the final result, including links and artifact references. Ending the call should not suppress the written handoff. Continued execution itself is not the reported failure. No root cause is asserted.