Codex Update

6/7 Workaround until then. Check the version actually moved: b=$(codex --version); codex update; a=$(codex --version); echo "$b -> $a" If it didn't, pin the release: npm i -g @openai/[email protected] With an age gate on, npm then fails loudly (ETARGET) instead of quietly.

3/7 Fixed in 0.166.0: the updater now saves the script first and only runs it if curl succeeded. Same dead-proxy test: curl (7), a clear Error line, exit code 1, version unchanged. Correct. Fix by etraut-openai; root cause traced by jiang1997 & abruption. github.com/openai/codex/pull…

2/7 The old bug (standalone installs, 0.165.0 and earlier): the updater ran curl ... | sh. If curl fails, sh gets an empty script, exits 0, and Codex prints success. I cut the network with a dead proxy: curl error (7), "🎉 Update ran successfully!", exit 0, still 0.165.0.

1/7 Half fixed: Codex's "Update ran successfully" message. 0.166.0 stops the standalone updater from claiming success when the download fails. On npm installs it can still say 🎉 when nothing changed, or after a downgrade. Tested on a clean Linux box, no login needed 🧵

507 👍: LSP in the CLI is Codex's top feature request. Two of the top five are about undoing work: - Bring back /undo (490) - /rewind to roll back both the chat and the code edits (230) Method: open enhancement issues in openai/codex, ranked by 👍, snapshot Oct 29. If one of these is yours, add your 👍 on the issue.

5/7 It looks load-sensitive. On a local 8-core Linux box the new build opened fine for me (UI mounted in 9.8 s). Others report it reproduces in dev containers too (MichaelDevine, SyncM1972 on GitHub). Quick retries that help some: disable/re-enable the extension (wrickout).

3/7 Why it happens: the extension gives its webview 30 s to report "ready", then shows the error. I unpacked both builds. That 30 s limit is identical. What grew is the webview: 539 MB / 19,524 files before, 723 MB / 22,544 files now.

2/7 The fix most people confirm: roll back to the last good build. code --install-extension [email protected] --force On VS Code 1.143.1 it installed in ~13 s and was marked pinned. Via GitHub user StevieDicks, who said reinstalling from the menu didn't work.

Codex CLI v0.164.0 cheat sheet: resume and fork sessions, piping into codex exec, profiles, worktrees, /compact, /init, /presets, and remote control. Save this one.

5/8 Second trap: if Codex lives under ~/.local or nvm, ":minimal" = "read" may not cover its own binary: bwrap: execvp …/codex: No such file or directory A read rule for the install dir fixed it. Filed by GitHub user alma-iceee (+8): github.com/openai/codex/issu…