"Introducing gpt-5.3-codex" message shown frequently / many times
Resolved 💬 7 comments Opened Feb 7, 2026 by embedding-shapes Closed Apr 3, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
codex-cli 0.98.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.2
What platform is your computer?
Linux 6.18.6-2-cachyos x86_64 unknown
What terminal emulator and version are you using (if applicable)?
alacritty
What issue are you seeing?
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.2 if you prefer.
Choose how you'd like Codex to proceed.
1. Try new model
› 2. Use existing model
Seemingly 1/4 times or something I open codex, I see the above message and have to select "No, I still want to keep using the same model I've already said I want to use".
I think maybe this was supposed to only show once per user, but instead it seems to reappear. Seems to happen both when using codex in directories where you've used it before, and new directories.
What steps can reproduce the bug?
Open codex with gpt-5.2 set as your current model multiple times either in the same or different directories.
What is the expected behavior?
The message is presented once (or less times than currently at least) per user.
Additional information
_No response_
7 Comments
I'm now running my own fork of Codex as this message is getting in the way so much, could you please at least decrease the frequency of this? It keeps asking me to change the model and I can't find any workaround except patching the code itself, but I also don't want to keep maintaining my own fork just because of this bug.
@embedding-shapes, this message should appear only once. The preference is saved in your
config.tomlfile like this:Can you confirm that this is appearing in your config file? By any chance, are you modifying or deleting your config?
Many thanks for replying @etraut-openai
This is what my config has right now re notices:
And yes, I'm still seeing that maybe 10-20 times a day, starting codex 30-40 times, I'd estimate.
I always run codex with
codex --sandbox danger-full-access --dangerously-bypass-approvals-and-sandbox --searchFWIW, I see I missed explaining this in the initial description. I've confirmed other config values are used from the config, so doesn't seem to be the case the config cannot be read somehow and therefore using default values, other things are used correctly.Thanks for confirming that you have the
"gpt-5.2" = "gpt-5.2-codex"line in your config file. That should prevent the message from showing up.I'm not able to repro the problem, and we haven't received reports of this from other users, so there must be something specific about your configuration that's causing this. You may need to do some debugging on your own. Codex is open-sourced, so you could clone the repo, build it, and ask codex to try to help you debug the problem. Let us know if you find the cause.
Related: #11468
I get the prompt when using api key authentication and probably shouldn't be.
I just want to say I'm also getting this. Also, may I ask what
"gpt-5.2" = "gpt-5.2-codex"is supposed to mean? To be clear, I'm currently mostly usinggpt-5.2(not codex) so that's what I have selected.If you see
"gpt-5.2" = "gpt-5.3-codex"in the[notify]section of your config file, that means "the user has already been asked whether they want to upgrade fromgpt-5.2togpt-5.3-codex". If present, you should not see an introduction message or upgrade prompt if your configured model isgpt-5.2. If you were to then change your selected model togpt-5.2-codex(by adding the config linemodel = "gpt-5.2-codex") and relaunch, you'd see the introduction message and upgrade prompt, and regardless of whether you pick "yes" or "no", you'd see that"gpt-5.2-codex" = "gpt-5.3-codex"is added to the[notify]section.Let me know if that differs from what you're seeing.