Codex routing 5.3 codex to 5.2
Resolved 💬 7 comments Opened Feb 17, 2026 by GalToast Closed Feb 18, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Same issue as others. Cyber verified, routed to 5.2 base. 5.3 codex spark works for some reason though. Verified through rust logs.
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Same thing here. More than 24h has passed and still being routed to gpt 5.2. The work I was doing? TODO apps
Check if vscode need some update..."it's worked on my end":)
@GalToast & @aurindo10, can you check now? We just rolled out a fix, and I'd like to get a confirmation or two before I make a broad announcement.
@etraut-openai thank you. it's working now. sorry for the recurring posts. This model is so good I can't work without it.
If you experienced a downgrade from
gpt-5.3-codextogpt-5.2despite completing Trusted Access verification, access togpt-5.3-codexshould now be restored. This fix took longer than expected. The team needed to work through some deployment issues over the past day. The fix is now rolling out across our clusters.If you’ve completed Trusted Access verification and are still seeing a downgrade, please open a new bug report and provide details. Likewise, if you're having trouble with the verification process, please open a bug report.
This issue is related to new cybersecurity safeguards we’re implementing for
gpt-5.3-codexand future models. We’ve published additional documentation explaining these safeguards and why they’re necessary.We’re also rolling out client updates that provide clear messaging when a downgrade occurs. The latest CLI release (v0.102.0) includes this notification. Updated versions of the Codex IDE extension and app will be available shortly with the same messaging. The notification links directly to the new documentation and verification instructions.
We recognize that this rollout caused frustration. We’ll learn from this and aim for smoother releases going forward. Thank you for your patience while we worked through this.
Fixed on my end, thanks Team!
Closing out 👋