Verified Pro subscriber silently routed to GPT-5.2 instead of requested GPT-5.3-codex

[khaled-wsa]

What issue are you seeing?

After completing identity verification, I had normal gpt-5.3-codex access for two days. Then, without any change on my end, I was silently downgraded to gpt-5.2 not even gpt-5.2-codex. The downgrade has persisted for 22+ hours. No error, no warning; the CLI just quietly serves a different model.

Confirmed with:

RUST_LOG='codex_api::sse::responses=trace' codex exec
--skip-git-repo-check -s read-only -m 'gpt-5.3-codex'
'hi' 2>&1 >/dev/null | rg -o --replace '$1' '"model":"([^"]+)"' | head -n1

Output: gpt-5.2-2025-12-11
Expected: gpt-5.3-codex

What steps can reproduce the bug?

1. Be an ID verified ChatGPT Pro subscriber.
2. Use Codex normally on non-sensitive repos.
3. At some point, get silently downgraded.
4. Run the trace command above to confirm.

What is the expected behavior?

A verified Pro subscriber requesting gpt-5.3-codex should receive gpt-5.3-codex. If a downgrade happens, the CLI should surface the reason explicitly.

Additional information

• Affects multiple verified Pro users.
• The downgrade is sticky and doesn't self-resolve.
• If this is a safety classifier issue it needs tuning and users need transparency, not silent downgrades.

[github-actions]

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

• I’m being incorrectly routed to GPT-5.2. I'm pro user and cyber verified #11920
• Model routing mismatch: requesting gpt-5.3-codex returns gpt-5.2-2025-12-11 (verified via SSE response.created) #11867
• GPT-5.3-Codex being routed to GPT-5.2 #11842
• GPT-5.3-Codex being routed to GPT-5.2 #11561
• Selecting gpt-5.3-codex in Codex shows response.model = gpt-5.2-2025-12-11 #10953

Powered by Codex Action

[aurindo10]

Same here

[etraut-openai]

Thanks for reporting, and apologies for the inconvenience. We're aware of the issue and are actively working on a mitigation. I'll share updates as they become available.