codex - 💡(How to fix) Fix 404 "Model not found gpt-5.2" causes WebSocket fallback + reconnect loop in Codex CLI

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Codex CLI fails with a 404 Not Found error for the gpt-5.2 model and enters a reconnect loop. CLI should return a clear validation error immediately if the model alias is unsupported. error messaging should indicate supported/available model names

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.125.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.2

What platform is your computer?

windows

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

VS Code terminal

What issue are you seeing?

Codex CLI fails with a 404 Not Found error for the gpt-5.2 model and enters a reconnect loop.

Observed behavior: Falling back from WebSockets to HTTPS transport. unexpected status 404 Not Found: Model not found gpt-5.2

Then: Reconnecting... 2/5 Unexpected status 404 Not Found Model not found gpt-5.2

It appears the CLI either: references an invalid/removed model alias, or does not correctly resolve the configured model name.

The issue persists after fallback from WebSocket transport to HTTPS transport.

What steps can reproduce the bug?

What steps can reproduce the bug? Launch Codex CLI Configure/use model gpt-5.2 Start a normal coding session or request CLI attempts WebSocket connection Falls back to HTTPS Receives: 404 Not Found: Model not found gpt-5.2 CLI enters reconnect loop

What is the expected behavior?

What is the expected behavior?

Expected behavior: The configured model should resolve successfully, OR CLI should return a clear validation error immediately if the model alias is unsupported.

Additionally: reconnect retries should stop for permanent 404 model not found errors error messaging should indicate supported/available model names

Additional information

Falling back from WebSockets to HTTPS transport. unexpected status 404 Not Found: Model not found gpt-5.2

Reconnecting... 2/5 Unexpected status 404 Not Found Model not found gpt-5.2

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix 404 "Model not found gpt-5.2" causes WebSocket fallback + reconnect loop in Codex CLI