[ChatGPT Desktop][macOS][Voice] /feedback does not show a final success or failure confirmation

Open 💬 2 comments Opened Aug 25, 2026 by omarpinarecords
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

In a realtime Voice chat in the ChatGPT desktop app on macOS, the /feedback flow shows an uploading state and displays a Feedback ID, but it does not show a terminal confirmation afterward.

The user cannot tell whether the feedback text was accepted, whether diagnostics finished uploading, or whether the submission failed.

Environment

  • Product surface: ChatGPT desktop app → Work → realtime Voice
  • App version: 26.820.60940 (build 7119)
  • Platform: macOS 26.6.2, Apple Silicon (arm64)
  • Date reproduced: August 25, 2026
  • Feedback ID: 01a03aaa-755e-7a41-98b1-b1cb1d02eaa5
  • Feedback receipt state: NOT_PROVED because no final success confirmation appeared

Steps to reproduce

  1. Start a new realtime Voice chat in the ChatGPT desktop app.
  2. Run /feedback from that Voice chat.
  3. Enter feedback and submit it.
  4. Observe the uploading/progress dialog.
  5. Observe that the flow displays a Feedback ID.
  6. Return to the Voice chat and wait for the submission to finish.

Actual behavior

  • The flow displays that feedback is being sent.
  • It displays a Feedback ID.
  • No final Feedback uploaded confirmation appears.
  • No explicit failure message appears.
  • The normal follow-up guidance to reference the Feedback ID in a GitHub issue is not shown.
  • The user cannot distinguish:
  • feedback text accepted;
  • diagnostics still uploading;
  • diagnostics failed;
  • entire submission failed; or
  • submission completed but the confirmation UI was lost behind Voice.

Expected behavior

The Voice /feedback flow should always reach a durable terminal state:

  • Success: clearly confirm that feedback was submitted, show a copyable Feedback ID, and provide the normal next-step guidance.
  • Partial success: distinguish accepted feedback text from failed or pending diagnostic uploads.
  • Failure: clearly state that nothing was submitted, or identify the failed component and provide a bounded retry path.

Displaying the Feedback ID should not replace a final success, partial-success, or failure confirmation.

Impact

Users reporting Voice defects cannot verify whether OpenAI received their report or diagnostic data. Retrying risks a duplicate submission, while not retrying risks losing the report. The missing receipt also breaks the intended handoff from in-product feedback to a GitHub issue.

Related issues and duplicate distinction

  • #26654 reports the general feedback dialog closing without showing a Feedback ID.
  • #39892 reports a normal Codex task showing its task ID first and then an explicit diagnostics-upload failure.
  • This issue is specific to realtime Voice: the flow shows an uploading state and Feedback ID, then returns without either a final success confirmation or an explicit failure.

Privacy

The full screenshots are intentionally not attached because they show private Project and task names. No logs, trace files, account identifiers, private conversation content, or local paths are included.

Validation / close criteria

  • Voice /feedback always produces a visible terminal success, partial-success, or failure state.
  • The UI distinguishes the feedback report from diagnostic upload status.
  • A confirmed Feedback ID remains visible and copyable until dismissed.
  • The same result is observable while Voice remains active.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 days ago

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

  • #39892
  • #40584

Powered by Codex Action

omarpinarecords · 2 days ago

Thanks for the duplicate suggestions. I reviewed them and do not believe this Voice-specific report is a duplicate.

  • #39892 was reproduced in a normal ChatGPT Desktop Codex task, not in realtime Voice. In that earlier case, the flow displayed a task ID and then showed an explicit red submission error. Feedback submissions from normal tasks now appear to be working for me, so that earlier behavior may already be resolved; I will run a fresh non-Voice test and update #39892 separately. I am leaving it open until that verification is complete.
  • #40584 reports an upload timeout together with a reasoning-display problem. It does not describe the Voice-specific loss of the terminal confirmation UI.

This issue is limited to realtime Voice: the flow shows that feedback is being sent and exposes a correlation reference, but then returns to Voice without either the normal final success confirmation or an explicit failure. The surface, observed terminal state, and close criteria are therefore different from #39892 and #40584.