Codex one-click update right after an OpenAI release leaves Codex without its platform binary #16160

What happened

The desktop app offered a Codex update. I clicked it, and afterwards every Codex thread failed. The provider banner showed Codex app-server provider probe failed: Codex App Server process exited with code 1. and new turns failed with Failed to fork codex provider thread …. Nothing in the UI said that Codex itself was broken or how to fix it.

Diagnosis

1. The update ran while the release was still propagating. OpenAI published @openai/codex@0.160.1 at 18:33:51Z. Its platform package 0.160.1-linux-x64 is listed at 18:35:04Z. The provider update toast ran npm install -g --prefix <nvm node 22 prefix> --allow-scripts=@openai/codex @openai/codex@latest at 18:36:21Z (ws.rpc.server.updateProvider → ProviderMaintenanceRunner.runCommand, 1.8 s).
2. npm dropped the platform binary silently. The registry still returned 404 for the linux-x64 tarball at that moment. Because it is an optionalDependency, npm logged reify failed optional dependency and still exited 0. The result was a launcher with no binary: codex --version fails with Error: Missing optional dependency @openai/codex-linux-x64. Reinstall Codex: npm install -g @openai/codex@latest.
3. T3 Code showed only the exit code. The post-update refresh (probeCodexAppServerProvider) failed with CodexAppServerProcessExitedError: … exited with code 1, and the codex stderr with the actual cause never reached the UI. In runCommandAndVerify (apps/server/src/provider/providerMaintenanceRunner.ts) this most likely ends as unchanged, "could not verify the provider version". From that the user cannot tell that the install is broken and that simply re-running the update fixes it. I did not capture the toast text.
   Possible improvements:

• Before offering or running an npm-based update, check that the tarball for the current platform's optional binary package can actually be fetched, or retry or hold the update for a short window after the publish time.
• After an update, verify by running the binary (codex --version) and show its stderr. If the output contains Missing optional dependency, report the install as broken and offer to reinstall.
• Include the child's stderr in CodexAppServerProcessExitedError so the provider banner shows the real reason.

Steps to reproduce

Deterministic repro needs a release whose platform tarball is not fetchable yet. To simulate it:

1. Install Codex globally with npm on Linux x64. T3 resolves it as an npm-global install.
2. Remove <prefix>/lib/node_modules/@openai/codex/node_modules/@openai/codex-linux-x64. This is the state npm leaves behind after the 404.
3. Open T3 Code. The provider status shows Codex App Server process exited with code 1 without the underlying Missing optional dependency message, and Codex turns fail with Failed to fork codex provider thread ….
4. Run the same npm install again: the package is restored and Codex works.

Version

0.0.46-nightly.20261005.2689 (desktop, nightly channel)

Environment

Linux Mint 22.3 x64 (kernel 7.0.0), codex-cli 0.160.1 (npm global in an nvm Node 22.19 prefix, run with Node 24.21 / npm 11.19 from vite-plus on PATH), claude 2.1.289

Evidence

# npm debug log of the update (~/.npm/_logs/2026-10-05T18_36_21_420Z-debug-0.log)
7 verbose argv "install" "--global" "--prefix" "~/.nvm/versions/node/v22.19.0" "--allow-scripts" "@openai/codex" "@openai/codex@latest"
69 silly placeDep node_modules/@openai/codex @openai/codex-linux-x64@0.160.1-linux-x64 OK for: @openai/codex@0.160.1 want: npm:@openai/codex@0.160.1-linux-x64
78 http fetch GET 404 https://registry.npmjs.org/@openai/codex/-/codex-0.160.1-linux-x64.tgz 58ms (cache skip)
79 verbose reify failed optional dependency ~/.nvm/versions/node/v22.19.0/lib/node_modules/@openai/codex/node_modules/@openai/codex-linux-x64
88 verbose exit 0

# registry publish times (npm view @openai/codex time)
0.160.1            2026-10-05T18:33:51.980Z
0.160.1-linux-x64  2026-10-05T18:35:04.137Z

# codex afterwards
Error: Missing optional dependency @openai/codex-linux-x64. Reinstall Codex: npm install -g @openai/codex@latest

# server trace, span tree of the update (local time = UTC+2)
ws.rpc.server.updateProvider
 └ ProviderMaintenanceRunner.runProviderUpdate      Success (1869 ms)
    └ refreshInstance → checkCodexProviderStatus
       └ probeCodexAppServerProvider                Failure: CodexAppServerProcessExitedError: Codex App Server process exited with code 1

Related issues

#14249 (Codex update leaves the install wrong) is related, but its cause is pnpm minimumReleaseAge; here npm silently drops a failed optional platform dependency. Not a duplicate.

Fix applied or workaround

Re-ran npm install -g --prefix <same prefix> @openai/codex@0.160.1 once the tarball was available (the platform package was then installed and codex --version worked), then restarted the desktop app. Re-clicking the provider update should have the same effect.

Filed by

Claude Code (Claude Opus 5.5) via t3 triage