Codex Mac feedback upload times out and reasoning fails to display

Resolved 💬 4 comments Opened Aug 25, 2026 by phtrillaud-netizen Closed Aug 26, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.818.61809

What subscription do you have?

chat GPT plus

What platform is your computer?

Darwin 25.5.0 arm64 arm bash-3.2$

What issue are you seeing?

The feedback upload keeps loading and eventually times out. The reasoning section sometimes fails to load or display.

What steps can reproduce the bug?

When I submit feedback in the Codex Mac app, the upload eventually times out. I also sometimes see that the reasoning section fails to load or display.

Steps to reproduce:

  1. Open the Codex Mac app.
  2. Start or open a conversation.
  3. Submit feedback or a request.
  4. Wait for the upload/response to complete.

Actual result:
The upload times out, and the reasoning content may fail to display.

This issue occurs intermittently. I do not have a code snippet because the problem happens in the Codex app interface.

What is the expected behavior?

The feedback should upload successfully without timing out, and the reasoning content should load and display normally.

Additional information

The issue persists after retrying. I can provide screenshots or a session ID if needed.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 3 days ago

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

  • #39892
  • #40553

Powered by Codex Action

phtrillaud-netizen · 2 days ago

Correction and clarification of my original report:

#39892 matches the feedback upload failure, but #40553 does not match the
reasoning issue.

The reasoning issue is not about raw reasoning content failing to display.
It concerns a failure to detect architectural drift during a long,
multi-document task.

The task involved an email, a PDF, and several dependent examples. Codex
handled each human correction locally, but did not reconstruct the global
document architecture. Each correction produced another plausible local
repair that created a contradiction elsewhere. I had to correct Codex four
times before it returned to the original plan and restored the intended
roles and ordering of the documents.

Expected behavior:
After multiple corrections affecting the order, medium, or function of
dependent deliverables, Codex should detect a risk of global architectural
drift, pause local execution, reconstruct the canonical plan, and consider
whether a deeper reasoning pass is needed.

The feedback submission failure occurred while I was trying to report this
reasoning issue. Three submissions through Help > Feedback failed after
approximately 11 seconds with:

failed to upload feedback to Sentry: operation timed out

The failure reproduced on two different networks and after restarting the
app.

Therefore:

  • #39892 is a duplicate only for the feedback-upload failure.
  • #40553 is not a duplicate of the architectural-drift issue.

Le mar. 25 août 2026 à 12:08, github-actions[bot] @.***>
a écrit :

github-actions[bot] left a comment (openai/codex#40584) <https://github.com/openai/codex/issues/40584#issuecomment-5408855276> Potential duplicates detected. Please review them and close your issue if it is a duplicate. - #39892 <https://github.com/openai/codex/issues/39892> - #40553 <https://github.com/openai/codex/issues/40553> Powered by Codex Action <https://github.com/openai/codex-action> — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/40584?email_source=notifications&email_token=CMQUDWJR7XNPH3XFXMPKQV35LVQR7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBQHA4DKNJSG43KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5408855276>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CMQUDWKMSW4QXJLAITJYHF35LVQR7AVCNFSNUABFKJSXA33TNF2G64TZHM4TMNJUGE2TMNBZHNEXG43VMU5TKMRUGQ3DENZVGQ2KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CMQUDWKURV2ZJ63TSDPVKQ35LVQR7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBQHA4DKNJSG43KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CMQUDWPAXPGWVWR3TH4VXAT5LVQR7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBQHA4DKNJSG43KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: @.***>
nos1609 · 2 days ago

Independent Windows ARM64 confirmation on the same Desktop release family:

  • Store package: 26.818.8289.0
  • Desktop release: 26.818.61809
  • two in-app feedback attempts produced no durable final success receipt;
  • no successful-upload marker or retry object was found afterward;
  • the local Sentry queue was empty, which cannot distinguish successful acceptance from a report dropped before durable queuing.

The detailed sanitized evidence is recorded in #39892:
https://github.com/openai/codex/issues/39892#issuecomment-5410774900

This confirms that the feedback failure is cross-platform and that the current UI does not provide an auditable delivery state. No feedback text, logs, account data, local paths, hostnames, or project names are included.

phtrillaud-netizen · 2 days ago

To keep the two reports separate, the architectural-drift issue is now tracked independently in #40849.

This issue (#40584) should be treated as concerning the feedback upload and delivery-state failure, which overlaps with #39892. The distinct failure to reconstruct a global plan across dependent deliverables is documented in #40849.

Please use #40849 for discussion and triage of the architectural-drift behavior.