[macOS app] In-conversation feedback upload fails after a Feedback ID is generated
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.825.32147
The About dialog identifies the app as ChatGPT — Powered by Codex & OWL and shows a release date of Aug 28, 2026.
What subscription do you have?
ChatGPT Pro
What platform is your computer?
macOS 26.6.2 on a 16-inch MacBook Pro with Apple M5 Max and 128 GB RAM (Apple silicon).
What issue are you seeing?
When I use the in-conversation Feedback flow to report a bug, submitting the feedback fails. The app displays the following dialog:
Feedback upload failed
The upload failed, but your Feedback ID is unchanged:
01a049cd-4178-7b72-b7a4-0935df42b272
The UI therefore reports that the feedback payload was not uploaded even though a Feedback ID remains visible. This makes it unclear whether the report reached OpenAI and prevents reliable use of the built-in feedback flow.
What steps can reproduce the bug?
- Open an existing conversation in the Codex app.
- Start the in-conversation Feedback flow to report a bug in that conversation.
- Submit the feedback.
- Observe the “Feedback upload failed” dialog while the same Feedback ID remains displayed.
I observed this occurrence in the current session. I have not confirmed whether every feedback submission fails.
What is the expected behavior?
The feedback should upload successfully and the app should show an unambiguous success confirmation. If a temporary upload error occurs, retrying should reliably resubmit the existing feedback payload without leaving uncertainty about whether the report was received.
Additional information
- Feedback ID:
01a049cd-4178-7b72-b7a4-0935df42b272 - The error occurred while reporting a bug from inside a conversation, not while submitting a GitHub issue.
- No device serial number or other sensitive identifiers are included in this report.
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
No source file, test, or entry point is named in the report. Start by locating the macOS in-conversation Feedback flow and its upload error handling, then reproduce the failure; done means successful submission and an unambiguous confirmation, with retry behavior that does not leave the feedback status uncertain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100