codex - 💡(How to fix) Fix Codex Desktop auto-selects gpt-5.2-codex for ChatGPT Plus accounts and every new thread fails

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

{"type":"error","status":400,"error":{"type":"invalid_request_error","message":"The 'gpt-5.2-codex' model is not supported when using Codex with a ChatGPT account."}} 5. The thread fails immediately with the unsupported-model 400 error

Code Example

{"type":"error","status":400,"error":{"type":"invalid_request_error","message":"The 'gpt-5.2-codex' model is not supported when using Codex with a ChatGPT account."}}
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using?

26.519.81530 (3178)

What subscription do you have?

ChatGPT Plus

What platform is your computer?

macOS 26.4.1 (Apple Silicon)

What issue are you seeing?

Every new Codex Desktop thread is being created with gpt-5.2-codex as the active model, and requests immediately fail with:

{"type":"error","status":400,"error":{"type":"invalid_request_error","message":"The 'gpt-5.2-codex' model is not supported when using Codex with a ChatGPT account."}}

This happens even though:

  • the app is fully updated
  • I create completely new threads
  • I reset local Codex caches/storage/state
  • I changed local global agent mode from custom to auto

Steps to reproduce

  1. Open Codex Desktop on macOS
  2. Create a brand new thread
  3. Do not manually choose a model
  4. Send any prompt
  5. The thread fails immediately with the unsupported-model 400 error

What is the expected behavior?

New threads should default to a model actually supported for ChatGPT accounts, or unsupported models should never be auto-selected.

What have you already tried?

  • App restart
  • New threads
  • Local state DB cleanup
  • Local Storage / Session Storage / SharedStorage reset
  • Global state reset from agent-mode=custom to agent-mode=auto

Additional evidence

A newly created session still records turn_context.model = "gpt-5.2-codex" on the latest app/CLI pipeline.

Relevant local evidence:

  • app version: 26.519.81530 (3178)
  • session cli_version: 0.133.0
  • new session turn_context.model: gpt-5.2-codex

I can provide the session JSONL snippet if needed.

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