Repository navigation
Episode 4: new release, familiar queue bug. Repair 2.4 for Codex VS Code 26.930.61225
Codex has another update. I downloaded the official Windows x64 package, compared the shipped files, reran the regression suite, and prepared my fourth community patch.
How many episodes until OpenAI joins the conversation? Grab some popcorn. 🍿
What actually improved
The bundled CLI moved from 0.160.0 to 0.160.1. There is a useful fix: preserving SYSTEMROOT, TEMP, and TMP when remote stdio MCP servers are launched on Windows with explicitly configured remote environment variables.
Official change: openai/codex#51121
Other observed changes include build metadata, a CLI version string, and analytics grouping of aeon_child as agent_created_thread. Some UI modules have different string identifiers; I have not validated their UI behavior.
And the follow-up queue?
It survived the update. So did the defects.
out/extension.jsis byte-for-byte identical to 26.930.51102.- The queue coordinator, storage adapter, host storage class, and submission-preparation function match after identifier normalization.
- All 68 coordinator members match: no added, removed, or changed members.
Some bundle filenames changed. The reviewed queue logic did not.
Controlled tests against the official code still reproduce:
- An undelivered message disappearing after an empty storage refresh.
- A restored pending message being dispatched again, despite positive delivery evidence.
- Invalid JSON
undefinedafter successful send-lock release.
Consistency is good. I was hoping for a different kind of consistency.
Tests and results
| Suite | Result |
|---|---|
| Canonical regression suite, Node | 94/94 |
| Same suite, Electron | 94/94 |
| Real CLI 0.160.1 app-server protocol checks | 16/16 |
| Independent review of another public patch, Node | 19/19 |
| Same independent checks, Electron | 19/19 |
That is 242 successful check executions, not 242 distinct scenarios. The canonical suite includes negative controls that pass when they reproduce an original defect, alongside repair, compatibility, and packaging checks. These totals do not mean the official extension is fixed.
Coverage includes concurrent writers, two windows across 180 cycles and three seeds, CAS retries, stale snapshots, removals and Undo generations, identical text under distinct IDs, interrupt/resume cases, dead-owner recovery, process death during lock preparation, and server queue integration.
The CLI checks use a real app-server with a local synthetic provider and an isolated home, without production model calls.
The finished package accounts for all 19,378 original archive entries, modifies only six declared entries, and adds six repair/backup entries. No files are missing. The official CLI and unrelated entries are hash-verified. Packaged and installed host startup checks passed in Node and Electron.
And yes, there is a negative startup test for the wrong queue-store.cjs filename. We have already had that plot twist.
Fourth patch: repair 2.4
Target: Codex VS Code extension 26.930.61225, Windows x64.
The repair uses a separate atomic journal with revisions and compare-and-set retries, so stale Memento snapshots cannot replace the authoritative queue and competing writers cannot silently overwrite each other's changes. It retains the existing coordinator and the official CLI 0.160.1.
The public download contains repair sources, tests, and an installer that downloads and verifies the official extension before building locally. It contains no personal settings, saved conversations, credentials, or redistributed official extension bundles.
Download and technical report: https://github.com/IveSan83/codex-vscode-queue-repair/releases/tag/v2.4.0
Source: https://github.com/IveSan83/codex-vscode-queue-repair
Ongoing investigation: openai/codex#50980
Previous patches: 2.1 for 26.930.31428, 2.2 for 26.930.31730, 2.3 for 26.930.51102.
The new patch is installed and active locally. The initial post-restart log sample contains no send-lock, undefined-JSON, or journal errors. That is an initial live check, not comprehensive UI certification. WSL flicker, Remote SSH lifecycle issues, Desktop command stalls, and older-CPU crashes are separate reports and are not claimed fixed by this patch.
OpenAI, we can wrap up the series now
Tibo announced 28 days of improvements or a full usage-limit reset: https://x.com/thsottiaux/status/2106845241357824205
Here is a candidate for an improvement of the day: fixing this queue. The reproduction, regression suite, and patch are ready for review.
As for me, I think a lifetime supply of usage resets would be fair. Or at least the head of QA's salary. I have been doing community QA for OpenAI for almost a week; we just need to sort out the employment paperwork. 😄
Which arrives first: an official fix, a maintainer reply, or community patch number five?
To be continued. Keep the popcorn handy. 🍿
Search terms: Codex VS Code queue fix, disappearing messages, duplicate follow-ups, stuck sending, Memento race, undefined is not valid JSON, 26.930.61225.