[VS Code] Clarify delivery of Astra catalog fix #42874: latest stable bundles CLI 0.153.0 and cannot self-update

What version of the IDE extension are you using?

openai.chatgpt 26.901.22334 (stable, win32-x64); bundled executable reports codex-cli 0.153.0

What subscription do you have?

Custom OpenAI-compatible API provider; not a verified ChatGPT subscription entitlement issue.

Which IDE are you using?

Visual Studio Code 1.136.1, x64 (stable)

What platform is your computer?

Windows x64

What issue are you seeing?

The latest stable VS Code extension available to this Windows x64 installation still reports codex-cli 0.153.0 for its bundled runtime. I would like to understand when the Astra model-catalog visibility fix discussed in #42874 reaches the IDE extension, and the supported update path in the meantime.

The system-wide codex command in this setup is only a wrapper around the extension's bundled binary, not a separate npm/Homebrew installation. Running codex update therefore fails with:

Error: Could not detect the Codex installation method. Please update manually: [https://developers.openai.com/codex/cli/](https://developers.openai.com/codex/cli/)

I understand a merged CLI fix does not automatically update an installed extension. I also do not want to infer patch inclusion solely from --version, since an extension build could contain backports. Could the team confirm the actual patch status and identify the extension release or tracking issue for this fix?

This is a request for clarification on runtime delivery/update behavior, not a verified diagnosis that the catalog change explains every missing-model case.

What steps can reproduce the bug?

1. Use openai.chatgpt 26.901.22334 (stable, win32-x64).
2. Run <extension-dir>\bin\windows-x86_64\codex.exe --version: output is codex-cli 0.153.0.
3. Running extension processes use this bundled executable; chatgpt.cliExecutable is empty.
4. Run codex update through a local wrapper invoking the same binary. It fails with the installation-detection error quoted above.
5. Marketplace query on September 8, 2026 returned 26.901.22334 as latest Windows x64 stable and 26.5901.22334 as latest prerelease. The prerelease has not been installed or inspected locally.

What is the expected behavior?

Could a maintainer clarify:

1. Does extension 26.901.22334 already include #42874 despite reporting CLI 0.153.0? If not, which extension release will include it, and is there a tracking issue or ETA?
2. Does this catalog fix affect custom API providers, or is model visibility controlled separately by a remote catalog/account eligibility?
3. Is using a newer external CLI via chatgpt.cliExecutable supported, and what compatibility constraints apply?
4. Could codex update tell users that the extension owns updates instead of reporting a generic detection error?

A version mapping or tracking link would help even if no ETA is available.

Additional information

Related: #42874 and #4323.

This concerns bundled-runtime delivery, not a claim that GPT-6 is unavailable to all extension users. Local configuration explicitly selects gpt-6-astra with a custom API provider. Model-list visibility, account eligibility, and actual upstream model execution have not been independently isolated. No extension files have been replaced or modified. Prepared with Codex assistance; personal paths, provider endpoints and credentials omitted.

Start with related issues #42874 and #4323, then inspect the bundled executable at \bin\windows-x86_64\codex.exe and the chatgpt.cliExecutable setting. Done means documenting whether the stable extension includes the fix, identifying the relevant release or tracking issue, and clarifying supported update and external-CLI paths.