Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Fix: Desktop App - Message send is delayed for ~8 seconds in new sessions after the latest update [3 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18264•Fetched 2026-04-17 08:30:38
View on GitHub
Comments
3
Participants
4
Timeline
6
Reactions
0
Author
JavierPiedraJavierPiedra
Participants
hhwang39hhwang39jaewon-kim-devjaewon-kim-devJavierPiedraJavierPiedramiraclebakelasermiraclebakelaser
Timeline (top)
commented ×3labeled ×3

In the Codex desktop app, sending a message can take around 8 seconds before the message is actually sent.

This appears to have started after the latest update. It did not happen in older sessions before.

Root Cause

This makes normal back-and-forth use of Codex frustrating because even short messages feel blocked before they are sent.

Fix Action

Fix / Workaround

  • Happens in newer sessions created after the latest update
  • Did not happen in older sessions tested by the user
  • Not fixed by lowering reasoning
  • Seen with GPT-5.4 and Extra High, but reasoning level does not appear to be the cause
RAW_BUFFERClick to expand / collapse

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

26.415.21839

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

Summary

In the Codex desktop app, sending a message can take around 8 seconds before the message is actually sent.

This appears to have started after the latest update. It did not happen in older sessions before.

Environment

  • App: Codex desktop app
  • Codex version: 26.415.21839 (1763)
  • macOS: 26.3.1 (build 25D771280a)
  • Hardware: MacBook Air (Apple M3, 24 GB RAM)

Actual behavior

After pressing Enter to send a message, the message does not send immediately.

Observed behavior:

  • The spinner appears in the send button
  • The message remains pending for about 8 seconds
  • Lowering reasoning does not help

This is affecting sessions created after the latest update.

What steps can reproduce the bug?

Reproduction

Observed repro:

  1. Open Codex desktop
  2. Open a newer thread created after the latest update
  3. Type a normal message
  4. Press Enter
  5. Observe the spinner in the send button and a delay of about 8 seconds before the message is sent

Additional observation:

  • In a brand-new thread, the first message sent immediately
  • The second message in that same new thread then started taking a very long time to send

Scope / pattern

  • Happens in newer sessions created after the latest update
  • Did not happen in older sessions tested by the user
  • Not fixed by lowering reasoning
  • Seen with GPT-5.4 and Extra High, but reasoning level does not appear to be the cause

What is the expected behavior?

Expected behavior

Pressing Enter should enqueue and send the message immediately, or at least show near-instant client acknowledgment.

Additional information

Notes

This feels like client-side send latency rather than raw network latency.

Local diagnostics from the machine at the time:

  • Network path looked healthy in macOS logs
  • Codex renderer/helper processes showed noticeable CPU activity while the issue was occurring
  • No obvious network failure was visible from the local system logs

Impact

This makes normal back-and-forth use of Codex frustrating because even short messages feel blocked before they are sent.

If you want, I can also compress this into a shorter GitHub-style version, or turn it into a more technical issue with a small Additional diagnostics section at the end.

extent analysis

TL;DR

The issue can likely be mitigated by investigating and optimizing the Codex desktop app's client-side processing, potentially related to the rendering or helper processes.

Guidance

  • Investigate the CPU activity of Codex renderer/helper processes to identify potential bottlenecks or inefficient processing.
  • Verify if the issue persists when using a different reasoning level or model (e.g., GPT-4 instead of GPT-5.4) to isolate the cause.
  • Check for any recent changes in the Codex app's update that might be contributing to the client-side send latency.
  • Consider testing the app with a minimal or default configuration to see if the issue is related to specific settings or plugins.

Example

No specific code snippet can be provided without more information about the Codex app's internal implementation. However, if the issue is related to the rendering or helper processes, optimizing or refactoring the relevant code might help alleviate the latency.

Notes

The issue seems to be specific to the Codex desktop app and newer sessions created after the latest update. The fact that the first message in a brand-new thread sends immediately, but subsequent messages are delayed, suggests a potential issue with the app's internal state or caching mechanism.

Recommendation

Apply workaround: Investigate and optimize the client-side processing of the Codex desktop app, as the root cause appears to be related to the app's internal implementation rather than a network issue. This approach is recommended because the issue is specific to the app and newer sessions, and optimizing the client-side processing might help alleviate the latency.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Pressing Enter should enqueue and send the message immediately, or at least show near-instant client acknowledgment.

#container setup#orchestration issue#cache issue#memory leak#API versioning

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Fix: Desktop App - Message send is delayed for ~8 seconds in new sessions after the latest update [3 comments, 4 participants]