False positive: gpt-5.3-codex rerouted to gpt-5.2

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

• #11925
• #11920
• #11867
• #11842
• #11561

Powered by Codex Action

Same here

OpenAI is neglecting this issue. Even users who have completed the Cyber verification are still being forcibly routed to version 5.2. Moreover, they do not explicitly inform users about this. This could clearly constitute consumer deception. Although they acknowledge this issue and claim to be working on resolving it, it has remained unresolved for several days. It is reasonable to suspect that they have intentionally deprioritized this matter.

@ehgus8, I can assure you that we're not ignoring or neglecting this issue. It's a high priority for us to get this resolved, and we've been working hard to do so. I understand your frustration. I'll share more details when I'm able to. In the meantime, thanks for your patience.

@etraut-openai , Thank you for taking the time to reply and clarify this.
I appreciate hearing that you're actively working on resolving this issue as a high priority. Looking forward to any further updates you can share. Thanks again for your efforts.

@etraut-openai thank you. In my case I've observed the model in use is definitely 5.3 codex high (at least that's what it's telling me when I inspect the logs) but it's felt _out of character_ today as if I'm using 5.2 codex. It left half of the planned work unfinished and claimed it's done. Didn't want to attempt a slightly longer / complex (but doable) refactor. I wonder if this is because of some kind of silent rerouting or just my luck today.

I've thus far switched back to 5.2 xhigh; it's slow but working through the refactor diligently.

More than 24h has passed and I'm still being routed to 5.2. The working I was doing? TODO apps

Please, this is super critical, like, to just turn it off, it's so obvious too.. At least give us a warning, we are already verified and it does nothing..

If you experienced a downgrade from gpt-5.3-codex to gpt-5.2 despite completing Trusted Access verification, access to gpt-5.3-codex should 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-codex and 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.