Codex VS Code extension 26.928.31416 to 26.930.31730: pressing Enter clears the composer but the message never reaches the conversation (fixed in 26.930.41038)

Context

Source(s): https://github.com/openai/codex/issues/49988 Status: reported working by source, not reproduced by us.

Problem

About every second message vanished for a commenter, and several queued messages could disappear together. A commenter on Remote SSH found the lost messages missing from the saved conversation history too. Long prompts were lost with no error.

Error (redacted / normalized)

Symptom (no error text): after pressing Enter, the composer clears, but the message does not appear in the conversation and Codex does not respond. It happens even when Codex is idle; sending the same text several times eventually works.

GET /tbo/primary status=404 {"detail":"Not Found"}

[IpcClient] Received broadcast but no handler is configured method=thread-queued-followups-changed

[IpcClient] Received broadcast but no handler is configured method=query-cache-invalidate

Applies when

Codex VS Code extension 26.928.31416 (bundled Codex CLI 0.159.2), 26.928.40906, 26.930.21537 and 26.930.31730, and pre-release 26.5928.31416; VS Code 1.139 and 1.140; Linux (Ubuntu, Fedora, Debian, Arch, Mint), macOS, Windows, WSL and Remote SSH; reported 2026-10-01 to 2026-10-04.

Confirm it is this problem

1. code --list-extensions --show-versions | grep '^openai\.chatgpt@' → expect: one of the versions above.
2. Send a few short messages in a row → expect: some clear from the composer but never show up; the extension log shows the lines in error_samples.

Not this when / boundary

You are already on 26.930.41038 or later; see failed for the one report after the fix.

Root cause

Not explained in the thread. A contributor said the fix was merged on 2026-10-03 and released in extension 26.930.41038 the next day.

Variables

none.

Fix

1. Update the extension to 26.930.41038 or later. If the marketplace still offers an older build, install that version by name: code --install-extension openai.chatgpt@26.930.41038 --force, then rerun confirm 1 → expect: openai.chatgpt@26.930.41038. Several commenters confirmed messages went through again (one tested a long conversation on WSL for about an hour, one on Remote SSH), and another confirmed the later 26.51002.51308.
2. Until you can update: select the whole message with Ctrl+A, then press Enter → expect: a commenter said this sends reliably; delete the queued copy that appears afterwards.
3. Or go back to 26.917.62051 and restart extensions → expect: the original poster and several commenters said the messages stopped disappearing.

How to verify

Send five messages in a row → expect: each appears in the conversation and gets a response.

What did not work

Reloading the webviews or the window only helped for a while. Changing Follow Up Queue Mode from Queue to Steer did not help. Clicking the Send button worked for one commenter at first, but later also failed until VS Code was restarted. One commenter still saw the problem on 26.930.41038 over Remote SSH on Linux, while another Remote SSH user said it was fixed there. Going back to 26.917.62051 did not fix an already affected long conversation for one commenter on WSL; another on WSL had to go back to the pre-release 26.5917.62051.

Rollback

After step 3, update the extension again once a fixed version installs.

Risks

On 26.917.62051, a commenter's configured gpt-6.1-sol model failed with The 'gpt-6.1-sol' model is not supported when using Codex with a ChatGPT account., so going back costs newer models. Copy long prompts before you send them until the fix is installed (a commenter did this).

Verified scope

Codex VS Code extension 26.928.31416 to 26.930.31730, October 2026.

Becomes obsolete when

The affected versions are no longer offered. Open question: whether the Remote SSH report on 26.930.41038 was a separate problem; nobody answered the request to retest on 26.930.51102.