codex - 💡(How to fix) Fix Assistant changed Codex install method during update without confirmation

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…

When asked to update Codex to the latest version, the assistant attempted to update the local Codex CLI. After the update command failed with an installation-method detection error, the assistant proceeded to install a standalone user-level Codex binary under ~/.codex/packages/standalone and expose it through ~/.local/bin/codex, instead of asking before changing installation strategy.

Error Message

When asked to update Codex to the latest version, the assistant attempted to update the local Codex CLI. After the update command failed with an installation-method detection error, the assistant proceeded to install a standalone user-level Codex binary under ~/.codex/packages/standalone and expose it through ~/.local/bin/codex, instead of asking before changing installation strategy.

Root Cause

The assistant treated making the latest codex resolve in PATH as equivalent to updating the existing installation. Changing installation method is a material system decision and should require confirmation.

RAW_BUFFERClick to expand / collapse

Summary

When asked to update Codex to the latest version, the assistant attempted to update the local Codex CLI. After the update command failed with an installation-method detection error, the assistant proceeded to install a standalone user-level Codex binary under ~/.codex/packages/standalone and expose it through ~/.local/bin/codex, instead of asking before changing installation strategy.

Expected behavior

If the existing Codex binary is installed at /usr/bin/codex and the built-in updater cannot detect the install method, the assistant should stop and ask before using a different install method. It should either update the existing system binary in place with user-visible sudo approval, or explicitly ask whether a user-level standalone install is acceptable.

Actual behavior

The assistant installed Codex 0.135.0 as a standalone user install, created ~/.codex/packages/standalone, created ~/.local/bin/codex, added a PATH block to ~/.profile, and left /usr/bin/codex unchanged.

Impact

This created two Codex installations and changed PATH precedence, making the apparent update depend on shell resolution rather than properly updating the system install. It also wasted user time and tokens because the standalone install then had to be undone and replaced with a proper /usr/bin/codex update.

Root cause

The assistant treated making the latest codex resolve in PATH as equivalent to updating the existing installation. Changing installation method is a material system decision and should require confirmation.

Corrective action requested

When an updater cannot detect the install method, Codex should inspect the current binary location and ownership, identify the proper system-level replacement path, ask before changing install method, use a visible terminal or exact sudo command for root-owned paths, and verify that which codex still resolves to the intended system path after the update.

Final state after manual correction

The standalone install was removed, the PATH block was removed, /usr/bin/codex was updated in place to codex-cli 0.135.0, and a backup was created at /usr/bin/codex.0.130.0.bak. GPT 5.5 Medium

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…

FAQ

Expected behavior

If the existing Codex binary is installed at /usr/bin/codex and the built-in updater cannot detect the install method, the assistant should stop and ask before using a different install method. It should either update the existing system binary in place with user-visible sudo approval, or explicitly ask whether a user-level standalone install is acceptable.

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 Assistant changed Codex install method during update without confirmation