GPT-5.3-Codex being routed to GPT-5.2

[theBucky]

What version of Codex CLI is running?

codex-cli 0.99.0-alpha.10

What subscription do you have?

ChatGPT Pro

Which model were you using?

gpt-5.3-codex

What platform is your computer?

Darwin 25.2.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Ghostty

What issue are you seeing?

Both config.toml and TUI are set for gpt-5.3-codex, but the output and SSE captures show that the model name is actually gpt-5.2-2025-12-11.

What steps can reproduce the bug?

1. Set both config.toml and TUI to gpt-5.3-codex
2. Run RUST_LOG='codex_tui::chatwidget=info,codex_api::sse::responses=trace' codex
3. Send a prompt
4. log/codex-tui.log shows response.model is gpt-5.2-2025-12-11 from event response.created

What is the expected behavior?

to actually use gpt-5.3-codex

Additional information

No response

[github-actions]

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

• models mismatch #11187
• gpt-5.2 stopped working - requests routing to gpt-5.1-codex-max instead #9039
• Unable to use gpt-5.2 xhigh #9035

Powered by Codex Action

[theBucky]

feedback was submitted: 019c4294-e78a-7da0-bfd9-08e5ebb3bec2

[theBucky]

Some context:

Was working fine since the release of 5.3-codex. This "misrouted" behavior started occurring approximately 5 hours before this issue was reported.

[yowave]

Same, gpt-5.3-codex routes to gpt-5.2-2025-12-11.

[isbee]

% RUST_LOG='codex_api::sse::responses=trace' codex exec --sandbox read-only --model gpt-5.3-codex 'ping' 2>&1 \
    | grep -m1 'SSE event: {"type":"response.created"' \
    | sed 's/^.*SSE event: //' \
    | jq -r '.response.model'
gpt-5.2-2025-12-11

Same here. I'm also using Pro plan, but I can't access latest model :(

[theBucky]

@etraut-openai did my account get flagged or something? A bit of updates will be nice :(

[alexdotpink]

@theBucky I do believe it's an account specific issue. Tried on my personal Pro account, and got gpt-5.2-2025-12-11, then tried the exact same command using my work account, and got gpt-5.3-codex.

[theBucky]

@theBucky I do believe it's an account specific issue. Tried on my personal Pro account, and got gpt-5.2-2025-12-11, then tried the exact same command using my work account, and got gpt-5.3-codex.

Same, just curious if this is intentional because I triggered something, or just some bugs in infras. Hopefully the latter.

[yowave]

@theBucky it shouldn't be intentional. If you request model X you should either get model X or an error saying you can't use model X.
Silently swapping models breaks reproducibility and makes debugging a nightmare since you end up questioning your prompts/workflow when the real issue is you're running on a different model.

[VividNightmareUnleashed]

this problem again, exactly as it happened when 5.2 codex rolled out.

Pro plan