Disable Codex prompting me to update npm package version

Resolved 💬 8 comments Opened Mar 11, 2026 by stevus Closed Mar 11, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

CLI

What feature would you like to see?

Allow me to turn off the

╭─────────────────────────────────────────────────╮
│ ✨ Update available! 0.111.0 -> 0.113.0         │
│ Run npm install -g @openai/codex to update.     │
│                                                 │
│ See full release notes:                         │
│ https://github.com/openai/codex/releases/latest │
╰─────────────────────────────────────────────────╯

especially if updates are coming out almost daily.

Additional information

_No response_

View original on GitHub ↗

8 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#13262

Powered by Codex Action

stevus · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate. * Update prompt fails because it does not include sudo. #13262 _Powered by Codex Action_

#13262 is unrelated & not a duplicate.

#13262 is an annoyance I encounter as well, however the objective of #14336 is to completely disable the update check + prompt. I would like to update Codex CLI at my own leisure and prefer not to receive update available notifications.

etraut-openai contributor · 4 months ago

There is a check_for_update_on_startup config key that you can set to false if you'd like to disable this.

stevus · 4 months ago

This configuration doesn’t work.

stevus · 4 months ago

Please reopen this issue or I can create a new one. Not sure why this was closed as the feature as I can tell is not supported.

stevus · 4 months ago

If you believe it to work, please provide specific examples.

etraut-openai contributor · 4 months ago

Have you added the following to your ~/.codex/config.toml file?

check_for_update_on_startup = false

Make sure it's not in a subtable in the toml file. It needs to be a top-level key.

stevus · 4 months ago

adding it to the very top of the file seemed to work. i had added it to other areas and the config passed while the updates were still being recommended, while adding it some tables I did see a failure. not sure what that's about but I no longer see the update available prompt.