Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex App regression after Apr 17 update: first message in a new thread sends immediately, follow-up messages stall on send button before inference starts [1 comments, 2 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#18439•Fetched 2026-04-18 05:54:45
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
chinmayingalagavichinmayingalagavi
Participants
chinmayingalagavichinmayingalagavigithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

What version of Codex App are you using?

26.415.30602 (1773)

What subscription do you have?

Not specified.

What platform is your computer?

macOS

What issue are you seeing?

After updating the Codex App on April 17, 2026, the first message in a brand-new thread sends immediately, but every subsequent message in that same thread stalls for about 5 seconds before inference starts.

The delay happens on the send button itself: after clicking send, the button shows a loading spinner before the model begins thinking/streaming. This does not look like model latency. It appears to be in the app submit path before the request is actually handed off.

Important details:

  • This was not happening on April 16, 2026 before the update.
  • It reproduces in the Codex App only.
  • The same prompts do not lag in CLI.
  • The first message in a new thread is fast; follow-up messages lag.
  • The issue is not typing lag. Typing is fine. The lag starts only after clicking send.

What steps can reproduce the bug?

  1. Open Codex App 26.415.30602 (1773).
  2. Start a new thread.
  3. Send a first message, for example hi.
  4. Observe that it sends immediately.
  5. Send a second message in the same thread.
  6. Observe that the send button shows a loading spinner for about 5 seconds before any thinking/response activity begins.
  7. Repeat with more follow-up messages in the same thread; the lag persists.
  8. Run the same prompt flow in CLI; CLI does not reproduce the delay.

What is the expected behavior?

Follow-up messages in an existing thread should submit immediately, as they did before the update, without a multi-second stall on the send button before inference starts.

Additional information

This looks like a regression in the app's conversation continuation/submit path rather than model inference speed.

Possible areas to inspect:

  • follow-up thread state assembly
  • request serialization / context packaging after turn 1
  • thread metadata sync before submit
  • app-side UI blocking in the submit path

A visual indicator of the symptom is that the spinner appears on the send control itself before the run starts, rather than a normal model-thinking state after submit.

extent analysis

TL;DR

The issue can likely be resolved by investigating and optimizing the conversation continuation/submit path in the Codex App, specifically focusing on follow-up thread state assembly, request serialization, or thread metadata sync.

Guidance

  • Inspect the follow-up thread state assembly process to ensure it's not causing unnecessary delays or blocking the submit path.
  • Verify if request serialization or context packaging after the first turn is introducing the lag, and consider optimizing this process.
  • Check if thread metadata sync before submit is causing the UI to block, and explore ways to improve this synchronization.
  • Review the app's UI code to ensure that the send button's loading spinner is not being triggered unnecessarily, causing the perceived delay.

Example

No specific code snippet can be provided without more context, but the investigation should focus on the areas mentioned above, such as thread state assembly, request serialization, and metadata sync.

Notes

The issue seems to be specific to the Codex App and not related to model inference speed, as evidenced by the lack of delay in the CLI. The fact that the first message in a thread sends immediately, but subsequent messages lag, suggests a regression in the app's conversation continuation/submit path.

Recommendation

Apply a workaround by optimizing the conversation continuation/submit path, as the issue appears to be a regression introduced in the recent update. This approach is recommended because it targets the likely root cause of the problem, rather than trying to upgrade to a potentially non-existent fixed version.

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…
#inference speed#authentication setup#request error#file not found#serialization error

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 Codex App regression after Apr 17 update: first message in a new thread sends immediately, follow-up messages stall on send button before inference starts [1 comments, 2 participants]