[ChatGPT Desktop][macOS][Voice] /feedback does not show a final success or failure confirmation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
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(build7119) - 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
- Start a new realtime Voice chat in the ChatGPT desktop app.
- Run
/feedbackfrom that Voice chat. - Enter feedback and submit it.
- Observe the uploading/progress dialog.
- Observe that the flow displays a Feedback ID.
- 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
/feedbackalways 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The payload names no repository files, entry points, or tests; begin by locating the macOS desktop realtime Voice /feedback flow and its upload-progress handling. Confirm the work is done when the flow visibly preserves a copyable Feedback ID and reaches an explicit success, partial-success, or failure state while Voice remains active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100