codex - 💡(How to fix) Fix Feature request: Show bundled/compatible Codex CLI version in VS Code Marketplace Overview notes [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19991Fetched 2026-04-29 06:24:03
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2

Root Cause

A user sees a new Codex CLI feature announced or documented, then checks the VS Code extension and cannot tell whether the installed Marketplace version already includes that runtime. The extension version alone is not enough because the numbering schemes differ.

RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

IDE Extension (VS Code)

What feature would you like to see?

Please include the bundled or compatible Codex CLI / app-server version for each VS Code extension release, and surface that information in the VS Code Marketplace listing — ideally in the Overview notes and/or Version History.

Right now the VS Code extension uses a different versioning scheme than the Codex CLI and desktop/app surfaces. That makes it hard to answer questions like:

  • Which Codex CLI / engine version is bundled with this extension release?
  • Does this IDE release already include support for a newly shipped CLI feature?
  • If behavior differs between CLI and IDE, am I actually comparing the same runtime generation?

Requested UX

At minimum, for each extension release, show:

  • extension version
  • bundled / compatible codex-cli version
  • optionally, app-server/engine build metadata if that is the more accurate internal compatibility unit

Suggested placement

  • VS Code Marketplace Overview tab
  • VS Code Marketplace Version History entries
  • optionally, an in-product command such as Codex: Show bundled CLI information

Why this would help

  • makes feature availability easier to understand across CLI, desktop, and IDE
  • reduces debugging confusion when the extension and standalone CLI are on different runtime versions
  • improves release clarity for users trying to track newly shipped capabilities
  • helps security-conscious and enterprise users identify what runtime is actually embedded in the extension

Concrete example

A user sees a new Codex CLI feature announced or documented, then checks the VS Code extension and cannot tell whether the installed Marketplace version already includes that runtime. The extension version alone is not enough because the numbering schemes differ.

Surfacing the bundled / compatible runtime version directly in the Overview and release notes would remove that ambiguity.

Additional information

I searched for related issues first. The closest one I found was #7670, which asked more broadly for extension-to-CLI mapping and bundled CLI visibility. My request here is narrower and specifically focused on developer experience in the VS Code Marketplace listing / Overview notes.

I’m specifically asking for release-facing compatibility/version information, not a change to the feature set itself.

The current Marketplace page already shows the extension version and update date, but not the bundled/compatible Codex CLI or engine version. Including that would make it much easier to understand whether newly shipped CLI capabilities are expected to be available in the IDE yet.

extent analysis

TL;DR

Display the bundled or compatible Codex CLI version in the VS Code Marketplace listing for each extension release to improve developer experience and reduce debugging confusion.

Guidance

  • Include the bundled/compatible codex-cli version in the Overview notes and/or Version History of the VS Code Marketplace listing.
  • Consider adding an in-product command, such as Codex: Show bundled CLI information, to provide easy access to this information.
  • Update the extension's release process to ensure that the bundled/compatible Codex CLI version is consistently documented and visible to users.
  • Review the current Marketplace page to determine the best placement for this information, considering the existing extension version and update date display.

Notes

The requested change is focused on improving the developer experience and release clarity, rather than modifying the feature set itself. The proposed solution aims to reduce ambiguity and confusion when comparing the extension and standalone CLI versions.

Recommendation

Apply workaround: Include the bundled/compatible Codex CLI version in the VS Code Marketplace listing to improve developer experience and reduce debugging confusion. This change can be made without modifying the underlying feature set, and it addresses the specific pain point of version ambiguity.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Feature request: Show bundled/compatible Codex CLI version in VS Code Marketplace Overview notes [1 participants]