Skip to content

Open VSX Codex for Windows releases not available since Version 26.721.30844 #39476

Description

@hestami-ai

What version of the IDE extension are you using?

Version 26.721.30844

What subscription do you have?

Pro

Which IDE are you using?

Windsurf / Devin

What platform is your computer?

Windows 11

What issue are you seeing?

In Open VSX marketplace for IDE Codex, the Windows download option is not available since the Version 26.721.30844. Published by
shijie-oai

https://open-vsx.org/extension/openai/chatgpt/26.814.41407

However, there does appear to be newer releases for the Microsoft VS Code marketplace for the Codex IDE extension for the latest releases.

What steps can reproduce the bug?

Go to Open VSX website for Codex.

Try to download Windows on the latest (or any release over the prior four weeks) and you will not see a Windows download option.

E.g., using the following link:

https://open-vsx.org/extension/openai/chatgpt/26.814.41407

Navigate to the download button under "resources" section on right hand side.

What is the expected behavior?

Previously, Windows was a selectable option. E.g., you can see on the following release.

https://open-vsx.org/extension/openai/chatgpt/26.5721.30844

Additional information

No response

Activity

  1. added
    bugSomething isn't working
    windows-osIssues related to Codex on Windows systems
    on Aug 19, 2026
  2. marc-caramello commented on Sep 8, 2026

    @marc-caramello

    Confirmed this independently on Windows x64 with VSCodium.

    • VSCodium is configured to use Open VSX.
    • On 2026-09-07, uninstalling and reinstalling the stable openai.chatgpt extension installed version 26.721.30844 for win32-x64. It was neither pinned nor installed as a prerelease.
    • Process inspection confirms that the running extension app-server is the bundled bin/windows-x86_64/codex.exe from that extension installation.
    • That executable reports codex-cli 0.146.0-alpha.3.
    • codex debug models --bundled returns eight models and no gpt-6-astra entry.
    • An IDE session explicitly configured with model = "gpt-6-astra" records originator=codex_vscode, source=vscode, provider=openai, and cli_version=0.146.0-alpha.3.
    • Its startup request fails with HTTP 400:
      "The 'gpt-6-astra' model requires a newer version of Codex. Please upgrade to the latest app or CLI and try again."
    • codex login status reports that the client is logged in using ChatGPT. The same account sees Astra on chatgpt.com, although I understand that availability can differ between Chat and Codex.
    • A newly fetched models_cache.json records client_version 0.146.0 and contains no Astra entry.
    • No custom model provider or base-URL override is configured. During the diagnostic check, OPENAI_BASE_URL was unset, no Headroom process was running, and nothing was listening on port 8787.
    • Checked on 2026-09-08: the Open VSX target endpoints for versions 26.825.51511 and 26.901.22334 return 404 for win32-x64, while their linux-x64 and darwin-arm64 target endpoints return 200.

    This means that a fresh Open VSX installation on Windows currently provides a Codex runtime older than Astra’s documented minimum version of 0.153.0.

    Could the team restore current win32-x64 publishing to Open VSX and confirm which IDE-extension release will first bundle a runtime containing the Astra catalog-visibility change from #42874, released in Codex 0.153.4?

  3. tmeindle commented on Oct 3, 2026

    @tmeindle

    This is still an issue and it is making my entire organization rethink using codex at all. We are stuck on this outdated version since our enterprise tools team guards against supply chain attacks and gates us behind open vsx. They block us from even visiting the official vs extension site and also lock down wsl.

    VS code integration is essential for our workflows. We all (60+ people spending $15,000+ monthly) use windows 11 and have been stuck on this old version of codex extension for 2 or 3 months now.

    There are CVEs on the current available open vsx windows version and I'm afraid info sec will ban the vulnerable version or it just stops working at which point we will have to convert our workflows to claude code or copilot.

    I'm wondering if fixing this issue is even on radar. if not I may as well start migrating before all our workflows break

    Thanks for your attention,
    Tim

  4. hestami-ai commented on Oct 3, 2026

    @hestami-ai
    Author

    @tmeindle - I read somewhere that you can download the latest Codex VSIX through regular Microsoft VS Code and install it whatever OpenVSX VS Code derivative you require. I have been using it successfully (so far) for Devin Desktop (formerly Windsurf).

  5. tmeindle commented on Oct 3, 2026

    @tmeindle

    @tmeindle - I read somewhere that you can download the latest Codex VSIX through regular Microsoft VS Code and install it whatever OpenVSX VS Code derivative you require. I have been using it successfully (so far) for Devin Desktop (formerly Windsurf).

    I work at a very large, highly locked down enterprise. Corporate infosec has the official vs code extension store blocked in vs code itself and in browsers. It is blocked on corporate firewall. Everything is gated through proxies. The version of vscode they allow us to install through their enterprise appstore is set up to connect to openvsx for extensions.

    Even if there was a way to install the updated version through another source, corporate policy forbids unauthorized software sources with penalties including termination of employment I would not risk it. Thanks for suggestion though

  6. hestami-ai commented on Oct 3, 2026

    @hestami-ai
    Author

    I'm not now nor ever suggesting subverting company / organization (cyber)security policy. I'm merely informing of another approach. On your end I might suggest having to escalate through your management and / or corporate IT helpdesk to let them know that this has been an issue now for I think a few months and as such could they investigate this alternative approach in a way that would or could be an officially supported method for receiving VS Code extension updates (perhaps specifically this OpenAI Codex one). (Assuming of course that you haven't already gone down this path.)

  7. marc-caramello commented on Oct 8, 2026

    @marc-caramello

    Yeah I was able to solve this problem just by switching to VS Code. I no longer use VS Code clones, I just use regular VS Code.

  8. maxiaotiao6 commented on Oct 10, 2026

    @maxiaotiao6

    I'm experiencing the same issue with the Codex extension in Positron IDE on Windows.

    Positron is a VS Code-based IDE designed for R and Python data science workflows. I use it for R programming and statistical analysis, and I rely on the Codex extension for AI-assisted coding.

    Unfortunately, the latest Windows version available through Open VSX is still 26.5730.61309, while newer versions are available for Linux and macOS.

    The Positron development team has confirmed that OpenAI has stopped publishing updated Windows builds to Open VSX:
    posit-dev/positron#16086

    Could the OpenAI team please resume publishing Windows builds to Open VSX?

    This would be very helpful for Windows users of Positron and other VS Code-based editors that rely on Open VSX.

    Is there an estimated timeline for resolving this?

    Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingextensionIssues related to the VS Code extensionwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions