Repository navigation
Releases
Repair 2.4 for Codex VS Code 26.930.61225 — fourth community queue patch
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.
Queue repair 2.3 - Codex 26.930.51102, Windows x64
Queue repair 2.3 — Codex VS Code 26.930.51102, Windows x64
This is the third published release of the independent queue repair.
Download
codex-vscode-queue-repair-2.3.0.zip: sources, builder and installer. The builder downloads the checksum-pinned official Windows x64 VSIX and applies the repair locally.codex-vscode-queue-test-results-2.3.0.zip: sanitized Node/Electron TAP logs, verification summary, package audit, component comparison and detailed investigation.SHA256SUMS-2.3.0.txt: archive checksums.
Extract the source ZIP and run START.cmd. Requirements: Windows x64, VS Code, Node.js and Python. Close all VS Code windows and reopen after installation. The package contains no account credentials, personal settings or machine-specific absolute paths. Author: IveSan83 (Eugene Bondarenko).
What the latest official build still reproduces
Controlled tests executing the actual shipped 51102 coordinator and response parser reproduce:
- A queued message disappears after an empty storage refresh representing stale snapshot delivery.
- A restored pending message is submitted again even when the controlled receipt lookup says it was already accepted.
- The send-lock release handler performs release and returns undefined. Serializing that result without a null fallback produces a response rejected by the frontend parser.
The third finding is a response-contract defect; it does not prove that the underlying lock stayed held or that it alone caused all delivery failures.
The coordinator, submission preparation function, queue adapter and host storage class match across official 31730, 41038 and 51102 after normalization of minified identifiers. All 68 coordinator members match. This is a comparison of the reviewed components, not a claim that the entire extension or all external dependencies are unchanged. The Windows native runtime remains CLI 0.160.0.
Repair-side improvement found during repeated testing
An earlier 91-test run passed in both runtimes. A repeated run exposed transient Windows EPERM while inspecting a competing writer's UUID owner file; the two-window stress case failed in both runtimes. Repair 2.3 adds bounded retries for owner metadata inspection. Live or unverifiable owners remain protected; persistent denial fails closed without changing the journal. Three deterministic fault-injection checks cover this behavior.
Final verification
- 94/94 Node tests and 94/94 Electron tests: 188 passes, zero failures, skips or cancellations.
- 180 two-window add/read/remove cycles per runtime: zero lost messages, zero resurrected messages, zero incorrect reads.
- Tests cover concurrent writers, stale snapshots, accepted-message replay, interruption and reload, identical-text messages with different IDs, removal/restore generations, owner/follower confirmation, real writer crashes and lock recovery.
- Three compatibility checks preserve upstream app-server receipt removal, owner/follower boundaries and subscription replacement cleanup.
- Cloud-history completion and plugin pagination checks execute current shipped functions.
- Finished VSIX inventory: 19,378 original entries, 19,384 packaged entries, 19,372 unchanged entries. No missing or unexpected files.
- Host storage startup and isolated journal read/write passed from both the completed VSIX and installed files in Node and Electron. Helper filenames and all modified-file hashes were verified.
- Following a manual VS Code restart, the running native process points to the repaired 51102 installation; installed hashes match and the observed startup log contains no undefined-JSON, send-lock-release, missing-module or unknown-queue-write errors.
These are headless code/filesystem tests with controlled transport. The brief restart observation is not a full live UI/model regression test. Cloudflare HTTP 403, unrelated metadata failures, MCP timeouts and ResizeObserver errors are outside this repair.
References
Queue repair 2.2 - Codex 26.930.31730, Windows x64
Queue repair 2.2 for Codex 26.930.31730 (Windows x64)
Repair author: IveSan83 (Eugene Bondarenko)
The latest reviewed official package still reproduces the tested stale-snapshot message-loss, pending-message replay and undefined JSON response defects. This release ports the repair to the exact 26.930.31730 win32-x64 bundle hashes and retains the existing private journal format.
Download
- codex-vscode-queue-repair-2.2.0.zip ? portable repair source, tests and installer. Extract into a new folder, close all VS Code windows, and run START.cmd. It downloads the official package, verifies its SHA-256, runs both regression gates, builds and audits the repaired VSIX, then installs and pins it.
- codex-vscode-queue-test-results-2.2.0.zip ? sanitized TAP logs for both runtimes, source hashes, verification summary, completed-package audit and the detailed release comparison.
- SHA256SUMS-2.2.0.txt ? checksums for the two ZIP assets.
The source/installer ZIP does not contain OpenAI's compiled extension, credentials, authentication, user messages or personal settings. The installer uses existing authentication and preserves a private queue backup locally. Do not upload that private backup.
Verification
- 88/88 mandatory tests in Node and 88/88 in VS Code's Electron/Node runtime: 176 executions with zero failures, skips or cancellations.
- Original-bug controls reproduce the official defects; repair scenarios check the patched code. This does not mean the unmodified official package passed repaired-storage tests.
- The suite covers actual shipped queue/response code, revision conflicts, owner/follower reconciliation, positive and uncertain receipts, Undo generations, four writer processes, dead-owner lock recovery and 180 seeded two-client cycles per runtime.
- The final VSIX preserves all 19,378 official entries, adds only six declared repair entries, retains 19,372 original entries byte for byte and preserves the native executable checksum. Its packaged host storage loads through real relative imports in both runtimes.
- The old wrong helper basename is a required failing control. The shipped helper is consistently out/queue-store.cjs.
The exact source/installer ZIP also passed a fresh extraction/setup verification without its own Git directory: both 88-test gates, full build and package startup passed. The previously verified official VSIX was supplied as the download cache. A local installation was verified against all 19,382 installed extension files, with zero missing or mismatched files (only VS Code-added __metadata is ignored). The extension is pinned; activation remains pending a full editor restart. These additional results are included in the test-results ZIP.
What changed upstream
Hosted Git metadata caching, bounded cloud-history readiness, incremental used-plugin history, cloud configuration and activity conditions changed. The four queue components retain their structure after minifier-identifier normalization, and the native executable is still codex-cli 0.160.0, byte-identical to 31428.
Detailed report: https://github.com/IveSan83/codex-vscode-queue-repair/blob/v2.2.0/reports/release-31730.md
Exact test registry: https://github.com/IveSan83/codex-vscode-queue-repair/blob/v2.2.0/REGRESSIONS.json
Previous upstream investigation: openai/codex#49834 (comment)
Scope
Supported installation: 26.930.31730, Windows x64. Different bundle hashes are rejected. Queue, Steer and Interrupt remain available. Saved uncertain sends remain paused for review. These are headless code/filesystem/controlled-transport and package checks; they do not guarantee live UI/model delivery, exactly-once external actions or faster model generation. Reopen all editor windows after installing.
This is the fifth affected version in the current report sequence. The requested upstream correction is authoritative revisioned queue persistence, safe delivery reconciliation and a valid void-response contract, with deterministic regression coverage.
Queue repair 2.1 - Windows x64
Repair author: IveSan83 (Eugene Bondarenko)
Source: https://github.com/IveSan83/codex-vscode-queue-repair
This release supports Windows x64 / openai.chatgpt 26.930.31428.
Download codex-vscode-queue-repair-2.1.0.zip, extract it into a new folder, close VS Code and run START.cmd. Requirements: stable VS Code with code in PATH, Node.js 22+ (x64), npm and Python 3.11+.
The installer downloads the pinned original extension from its official distribution URL, verifies its checksum, runs all 76 registered tests in both Node and VS Code's Electron/Node runtime, builds and checks the finished VSIX, and installs it. To build and verify without installing, run setup.ps1 -VerifyOnly.
The repair adds a separate atomic revisioned journal, concurrent-writer protection, durable retired IDs, dead-owner recovery, positive delivery reconciliation and canonical follower state. It also normalizes successful void JSON bridge responses. The official codex-cli 0.160.0 runtime is preserved.
The included stress test runs 180 two-window add/remove cycles per runtime with competing writes. Packaging checks every original archive entry and the real relative module dependency chain from the finished VSIX.
The ZIP contains this project's repair source, tests and scripts. It contains no OpenAI VSIX, user settings, private paths, queue contents or credentials. MIT license applies to the independent repair; see NOTICE.md for scope.
Automated tests cover storage, coordinator and package behavior using controlled transport. Live UI and production model delivery still need user verification. Unknown delivery remains paused for review; no exactly-once external action guarantee or model generation speed claim is made.
Related upstream storage report: microsoft/vscode#339391 . Composer draft/focus problems reported separately are outside this repair's verified scope.