Feature Request: Version Out of Date Alert

Resolved 💬 3 comments Opened Apr 17, 2025 by zer0cache Closed Apr 19, 2025

💡 Likely answer: A maintainer (tibo-openai, collaborator) responded on this thread — see the highlighted reply below.

I noticed there have been a few updates and new version launched since yesterday. It would be great for codex to let us know if we're running an older version and that we should upgrade once we boot it up.

View original on GitHub ↗

3 Comments

tibo-openai collaborator · 1 year ago

Yes, that would be nice and useful. Would accept a PR that detects this and displays a warning and allows to upgrade easily.

emcd · 1 year ago

While I agree with this feature request, there are some learnings to be had from the Claude Code rollout. The current installation instructions (npm i -g) can be quite toxic in conjunction with automatic upgrades and installations as the superuser (to get around permission restrictions on default NPM prefixes). Probably best to limit to manual upgrades until the instructions properly encourage people to install into environments from NVM, Mise, etc... or to set a user-writable NPM prefix.

scottleibrand contributor · 1 year ago

After a git pull of d61da89ed3e635d70e47c795ce29311ba6554696, I'm now getting:

(new_venv) ~/src/codex/codex-cli $ cd ~/src/codex/codex-cli/ && CODEX_DEV_DIR=~/src/codex/ npm run dev -- --auto-edit --notify

> @openai/codex@0.1.2504181820 dev
> npm run build:dev -- --auto-edit --notify


> @openai/codex@0.1.2504181820 build:dev
> NODE_ENV=development node build.mjs --dev && CLI_ROOT=$PWD && cd ~/src && NODE_OPTIONS=--enable-source-maps node $CLI_ROOT/dist/cli-dev.js --auto-edit --notify

✘ [ERROR] Could not resolve "boxen"

    src/utils/check-updates.ts:2:18:
      2 │ import boxen from "boxen";
        ╵                   ~~~~~~~

  You can mark the path "boxen" as external to exclude it from the bundle, which will remove this
  error and leave the unresolved path in the bundle.

(new_venv) ~/src/codex/codex-cli $