Windows: npm installs 0.121.0 but resolves to 0.119.0-win32-x64 binary
Resolved 💬 2 comments Opened Apr 20, 2026 by DesarrolloProtector Closed Apr 20, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
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/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
Analysis
The wrapper package @openai/codex@0.121.0 installs correctly, but it resolves to:@openai/codex-win32-x64@0.119.0-win32-x64
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.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This is a symptom of having multiple copies installed on your system. You'll need to find and remove the second copy.