openai.chatgpt on the Windsurf gallery is 2 months stale, leaving users on a CLI that cannot read their own Codex history
Summary
Devin/Windsurf resolves extensions from marketplace.windsurf.com. The newest
stable openai.chatgpt there for win32-x64 is 26.721.30844 (2026-07-24),
which bundles Codex CLI 0.146.0-alpha.3. The VS Code Marketplace is at
26.917.62051 (2026-09-23), bundling 0.155.0-alpha.16.3.
That is a ~2 month gap, and it is not cosmetic: the pinned CLI can no longer read
thread history written by current Codex builds, so chats fail to open with a fatal
deserialization error. Because the gallery has no newer build, affected users cannot
fix this through the editor's own updater.
The concrete failure
Codex CLI and the extension share CODEX_HOME (%USERPROFILE%\.codex). Newer builds
wrote subAgentActivity items with kind: "completed"; 0.146.0-alpha.3 only accepts
started / interacted / interrupted and aborts the whole thread:
Failed to resume chat
failed to deserialize stored thread item subagent-completed-<uuid>:
unknown variant `completed`, expected one of `started`, `interacted`, `interrupted`
Filed upstream against Codex: openai/codex#47959
(the wholesale-failure behavior is an OpenAI-side bug and is being reported there).
Verified on one install, same CODEX_HOME, same thread, listing items over the
app-server protocol:
| CLI build |
Result |
0.146.0-alpha.3 (bundled by 26.721.30844, newest on Windsurf gallery) |
fails: unknown variant \completed`` |
0.155.0-alpha.16.3 (bundled by 26.917.62051, VS Code Marketplace) |
40 pages / 1000 items, no error |
0.156.1 (standalone stable) |
40 pages / 1000 items, no error |
So the data is readable by every current build. Only the version the Windsurf gallery
serves cannot read it.
Environment
- Devin 1.126.0, Windows 11 Pro 26200 (x86_64)
extensionsGallery.serviceUrl: https://marketplace.windsurf.com/vscode/gallery
- Installed:
openai.chatgpt-26.721.30844-win32-x64, source: "gallery", not pinned,
auto-update not disabled
- Restarting the editor does not update it — there is nothing newer to fetch
Gallery state (queried 2026-09-24)
marketplace.windsurf.com, openai.chatgpt, win32-x64: 97 version rows,
44 stable. Newest stable 26.721.30844 (2026-07-24). Most recent publication of any
kind: 2026-08-05.
Impact
Users on Devin/Windsurf with Codex subagent history cannot open affected threads and
have no in-product way out. The remaining workarounds are hand-editing
thread_history_1.sqlite, sideloading a VSIX from the VS Code Marketplace (outside
the gallery Devin manages, so it can be reverted by a later reinstall), or installing
VS Code alongside. None of these are reasonable to ask of end users, and the first is
actively risky.
Ask
- Publish current
openai.chatgpt builds to the Windsurf gallery, and keep them
tracking upstream releases.
- If the gallery is going to lag, consider surfacing that to users — silently pinning
an AI extension to a months-old build has consequences beyond missing features when
that extension shares on-disk state with a separately-updated CLI.
openai.chatgpton the Windsurf gallery is 2 months stale, leaving users on a CLI that cannot read their own Codex historySummary
Devin/Windsurf resolves extensions from
marketplace.windsurf.com. The neweststable
openai.chatgptthere forwin32-x64is26.721.30844(2026-07-24),which bundles Codex CLI
0.146.0-alpha.3. The VS Code Marketplace is at26.917.62051(2026-09-23), bundling0.155.0-alpha.16.3.That is a ~2 month gap, and it is not cosmetic: the pinned CLI can no longer read
thread history written by current Codex builds, so chats fail to open with a fatal
deserialization error. Because the gallery has no newer build, affected users cannot
fix this through the editor's own updater.
The concrete failure
Codex CLI and the extension share
CODEX_HOME(%USERPROFILE%\.codex). Newer buildswrote
subAgentActivityitems withkind: "completed";0.146.0-alpha.3only acceptsstarted/interacted/interruptedand aborts the whole thread:Filed upstream against Codex: openai/codex#47959
(the wholesale-failure behavior is an OpenAI-side bug and is being reported there).
Verified on one install, same
CODEX_HOME, same thread, listing items over theapp-server protocol:
0.146.0-alpha.3(bundled by26.721.30844, newest on Windsurf gallery)unknown variant \completed``0.155.0-alpha.16.3(bundled by26.917.62051, VS Code Marketplace)0.156.1(standalone stable)So the data is readable by every current build. Only the version the Windsurf gallery
serves cannot read it.
Environment
extensionsGallery.serviceUrl:https://marketplace.windsurf.com/vscode/galleryopenai.chatgpt-26.721.30844-win32-x64,source: "gallery", not pinned,auto-update not disabled
Gallery state (queried 2026-09-24)
marketplace.windsurf.com,openai.chatgpt,win32-x64: 97 version rows,44 stable. Newest stable
26.721.30844(2026-07-24). Most recent publication of anykind: 2026-08-05.
Impact
Users on Devin/Windsurf with Codex subagent history cannot open affected threads and
have no in-product way out. The remaining workarounds are hand-editing
thread_history_1.sqlite, sideloading a VSIX from the VS Code Marketplace (outsidethe gallery Devin manages, so it can be reverted by a later reinstall), or installing
VS Code alongside. None of these are reasonable to ask of end users, and the first is
actively risky.
Ask
openai.chatgptbuilds to the Windsurf gallery, and keep themtracking upstream releases.
an AI extension to a months-old build has consequences beyond missing features when
that extension shares on-disk state with a separately-updated CLI.