Windows global npm update can leave codex-win32-x64 stale after @openai/codex update
What version of Codex CLI is running?
After the problematic update, codex --version still returned:
ext
codex-cli 0.124.0
The main npm package was already updated to @openai/codex@0.125.0.
What subscription do you have?
ChatGPT Pro
Which model were you using?
N/A - install/update issue before normal use.
What platform is your computer?
Windows x64
ext
Microsoft Windows NT 10.0.26200.0
Node.js v22.13.0
npm 11.10.0
PowerShell
npm global prefix: C:\usr\local
What issue are you seeing?
Updating Codex globally with npm can report success while leaving the native Windows platform package stale or partially replaced.
In this case, after updating to @openai/codex@0.125.0, the JS wrapper package was updated but the native package used by the wrapper was still effectively 0.124.0, so running codex --version continued to report codex-cli 0.124.0.
Observed state during investigation:
` ext
C:\usr\local\node_modules\@openai\codex\package.json
version: 0.125.0
C:\usr\local\node_modules\@openai\codex-win32-x64\package.json
version: 0.124.0-win32-x64
codex --version
codex-cli 0.124.0
`
A later direct reinstall attempt of the platform alias also left the global install in an incomplete/staging state for a while:
ext
C:\usr\local\node_modules\@openai\.codex-win32-x64-ZLHIbqty
C:\usr\local\node_modules\@openai\codex-win32-x64
At one point the target package existed but codex failed with:
ext
Error: Missing optional dependency @openai/codex-win32-x64. Reinstall Codex: npm install -g @openai/codex@latest
The
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗