feature: config setting to disable all model migration notices

Open 💬 3 comments Opened Mar 18, 2026 by 35C4n0r

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

What variant of Codex are you using?

codex cli

What feature would you like to see?

Codex version: codex-cli 0.115.0
Platform: Linux 6.8.0-87-generic x86_64 x86_64

Currently when we set

[notice.model_migrations]
"gpt-5.1" = "gpt-5.4"

We still get the migration notice to migrate to gpt-5.3-codex (which is to be expected, but only if the latest model were gpt-5.3-codex)

Codex just got an upgrade. Introducing gpt-5.3-codex.

  Codex is now powered by gpt-5.3-codex, our most capable agentic coding model yet. It's built for long-running, project-scale work, with mid-turn
  steering + frequent progress updates so you can collaborate while it runs (and it's faster too).

  Learn more: https://openai.com/index/introducing-gpt-5-3-codex/

  You can keep using gpt-5.1 if you prefer.

  Choose how you'd like Codex to proceed.

› 1. Try new model
  2. Use existing model

  Use ↑/↓ to move, press enter to confirm

The issue here is that different models try to resolve to different higher model, for example:
gpt-5.1 --notice_for--> gpt-5.3-codex
gpt-5.3-code --notice_for --> gpt-5.4

I propose that you let users use what they want to, we can add a new config setting under [notice] such as disable_all_model_migration_notice. If the user adds this setting to their config.toml, it will disable model_migration notices forever.

CC: @etraut-openai

Additional information

_No response_

View original on GitHub ↗

3 Comments

35C4n0r · 5 months ago

@etraut-openai, what are your thoughts on this ? Are you're fine with this, or do you want to spec it out a bit more ?
I see you removed the CLI tag, is this not a cli level change ? If you give a green light I can go ahead and try to create a PR for this.

etraut-openai contributor · 5 months ago

@35C4n0r, we generally prioritize features based on community upvotes. This feature request hasn't received any upvotes yet. We generally don't accept community PRs.

GunnGu · 5 months ago

I support this proposal.

In the Codex app, there are situations where the model can unintentionally switch to a frontier model that is not supported under a company’s contractual agreement. In my view, this migration notice feature allows minor user actions to trigger irreversible 403 errors, which is problematic.