Codex Desktop: pressing Enter occasionally sends the same message multiple times

Open 💬 7 comments Opened Apr 25, 2026 by mushan0x0

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

In Codex Desktop, hitting Enter once in the chat composer occasionally dispatches the same message 2-3 times. Confirmed it's not a hardware double-keypress — only happens in Codex Desktop, never reproduces in other apps with the same keyboard.

Symptoms in logs

Around the same window the desktop log shows a flood of:

[electron-message-handler] Request failed
  error={"code":-32600,"message":"thread not found: <id>"}
  method=thread/backgroundTerminals/clean
[electron-message-handler] Received turn/started for unknown conversation
  conversationId=<id>

Suggests internal thread/conversation state can get out of sync, after which the UI re-submits.

Expected

A single Enter dispatches exactly one message.

Environment

Codex Desktop 0.125.0-alpha.3
macOS 26.4.1 (arm64)

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 2 months ago

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

#18810
#19249
#18471

Powered by Codex Action

kunlunl · 1 month ago

Have the same issue.

kunlunl · 1 month ago

A somewhat unreliable tip: if I press the spacebar a few more times after each input, and wait a few seconds, and then press enter, it seems to avoid the problem (or greatly reduce the probability of it happening).

ptyin · 1 month ago

same

qq1060 · 28 days ago

I hit this again in Codex Desktop.

Feedback ID: 019eeea3-43f5-7283-8806-440b7a0e5ce1

Behavior:

Pressing Enter in the composer triggered the same prompt to be sent twice.
Clicking the send button does not reproduce it.
This happened in Codex Desktop on macOS.

Version:

Codex.app 26.616.51431 (4212)
Bundled CLI: codex-cli 0.142.0-alpha.6

This seems related to #19529 / #22409 / #22298.

tianoNero04 · 24 days ago

I reproduced this on macOS with Codex.app 26.623.41415 (build 4505) on 2026-06-27.

Additional log evidence:

A single submit produced two successful turn/start responses for the same conversation only 1 ms apart, with distinct request IDs.
In a new-conversation test, one submit created two different conversation IDs 275 ms apart. Both turns ran and consumed tokens.
Trying to stop the duplicated work then returned expected active turn id <A> but found <B>, confirming that two turns were competing for the same client state.
macOS had no custom accelerated key-repeat values, and no keyboard remapping tools were running.
After stopping both duplicated tasks, the next submit produced only one turn/start.

This looks like a Codex Desktop composer/thread-state race rather than a hardware Enter-key repeat. I have intentionally omitted local paths, conversation IDs, and request IDs from this public comment.

anton-muentz · 12 days ago

I am encountering this issue too, every day. I use the VS Code Codex extension.