Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Windows: npm installs 0.121.0 but resolves to 0.119.0-win32-x64 binary

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…

Fix Action

Fix / Workaround

Workaround Manual installation of the Windows binary from GitHub releases.

Code Example

npm install -g @openai/codex@0.121.0
codex --version

---

codex-cli 0.121.0

---

codex-cli 0.119.0

---

npm view @openai/codex version
# 0.121.0

npm list -g @openai/codex --depth=0
# @openai/codex@0.121.0

npm list -g @openai/codex-win32-x64 --depth=0
# @openai/codex-win32-x64@npm:@openai/codex@0.119.0-win32-x64

npx @openai/codex@0.121.0 --version
# codex-cli 0.119.0
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.119.0

What subscription do you have?

plus

Which model were you using?

gpt-5.2-codex

What platform is your computer?

Windows 11

What terminal emulator and version are you using (if applicable)?

Windows Terminal (WSL / PowerShell)

What issue are you seeing?

Bug: Windows npm install resolves to outdated binary (0.119.0) instead of 0.121.0 Environment

  • OS: Windows 10/11
  • Shell: PowerShell
  • Node: v22.17.0
  • nvm-windows: enabled
  • npm global prefix: C:\nvm4w\nodejs

What steps can reproduce the bug?

Steps to reproduce

npm install -g @openai/codex@0.121.0
codex --version

What is the expected behavior?

Expected result

codex-cli 0.121.0

Actual result

codex-cli 0.119.0

Additional information

Codex repeatedly asks to update even after installing 0.121.0.

Diagnostics

npm view @openai/codex version
# 0.121.0

npm list -g @openai/codex --depth=0
# @openai/[email protected]

npm list -g @openai/codex-win32-x64 --depth=0
# @openai/codex-win32-x64@npm:@openai/[email protected]

npx @openai/codex@0.121.0 --version
# codex-cli 0.119.0

Analysis The wrapper package @openai/[email protected] installs correctly, but it resolves to: @openai/[email protected]

So the actual binary executed is still version 0.119.0.

Conclusion This appears to be a packaging or resolution issue affecting the Windows x64 native binary.

Impact Users on Windows cannot upgrade beyond 0.119.0 via npm.

Workaround Manual installation of the Windows binary from GitHub releases.

extent analysis

TL;DR

The issue can be resolved by manually installing the Windows binary from GitHub releases to ensure the correct version of the Codex CLI is used.

Guidance

  • Verify that the @openai/codex-win32-x64 package is installed with the correct version by running npm list -g @openai/codex-win32-x64 --depth=0 and checking the version number.
  • Check the npm configuration to ensure that the global prefix is correctly set to C:\nvm4w\nodejs by running npm config get prefix.
  • Consider using the npx command with the specific version of @openai/codex to ensure the correct version is executed, e.g., npx @openai/[email protected] --version.
  • If the issue persists, try uninstalling the @openai/codex package and then reinstalling it using npm install -g @openai/[email protected].

Example

No code snippet is provided as the issue is related to package installation and resolution.

Notes

The issue appears to be specific to the Windows x64 native binary and may not affect other platforms. The manual installation of the Windows binary from GitHub releases is a temporary workaround until the packaging or resolution issue is resolved.

Recommendation

Apply the workaround by manually installing the Windows binary from GitHub releases, as this ensures the correct version of the Codex CLI is used.

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…
#installation#prompt template#agent execution#callback error#memory management

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 Windows: npm installs 0.121.0 but resolves to 0.119.0-win32-x64 binary