Repository navigation
fix(auth): drop the models retired for ChatGPT sign-in - #1580
Conversation
OpenAI retired gpt-5.4, gpt-5.4-mini and gpt-5.5 for ChatGPT sign-in only; API-key sessions still serve them. The ChatGPT and API-key defaults therefore differ on purpose, so they no longer have to match.
The gpt-6 and gpt-6.1 models offered fewer levels than the Codex backend serves (xhigh, or max for gpt-6-astra), while gpt-5.6-luna was offered ultra, which the backend does not serve.
|
Stack merge order: #1580 → #1581 → #1579. This repo keeps merged branches, so GitHub does not retarget the next PR on its own:
|
There was a problem hiding this comment.
Review · Request changes
The built-in ChatGPT model list says it follows the order the Codex service returns. It does not.
The service lists them as gpt-6.1-sol, gpt-6-astra, gpt-6-sol, gpt-6-luna, gpt-5.6-sol, then gpt-6.1-terra, then gpt-5.6-terra and gpt-5.6-luna. This branch puts gpt-6.1-terra third, ahead of gpt-6-sol, gpt-6-luna, and gpt-5.6-sol (src/auth/codex/constants.ts:31). The tests only check which reasoning levels each model allows, not the order of the list, so they still pass. Move gpt-6.1-terra to after gpt-5.6-sol.
The same catalog still offers gpt-5.5. This branch removes it, and the commit says ChatGPT sign-in retired it on October 14. If accounts can still select gpt-5.5, the fallback hides a model they can use. If the retirement notice is the source of truth, the comment on the list should stop saying the list is exactly what the service returns.
|
Triage: Unsure Asking a maintainer about:
|
Nothing pinned the list's order or its default, since the other tests read the constant, so a test now records what GET /codex/models listed for a ChatGPT Plus account on 2026-11-01. The comment says where the order comes from and that availability varies by plan and rollout, so it no longer implies every account is served this list. It also gives the reason the three models are left out: OpenAI retired them from Codex with ChatGPT sign-in, and API-key sessions are not affected.
0d8f6c2 to
d2c486f
Compare
|
Checked both findings against the backend and OpenAI's docs. The list is correct as it stood, so the order stays, and d2c486f fixes the comment and adds the missing test. Heads up that I force-pushed: an earlier commit, 0d8f6c2, moved gpt-6.1-terra to match the review before I had checked the backend. d2c486f replaces it. Order. gpt-6.1-terra is third. Repeat requests at client_version 0.165.0 and requests at 0.160.0, 0.164.0 and 0.166.0 all return this order. The order in the review, with gpt-6.1-terra after gpt-5.6-sol, did not come up. gpt-5.5. It stays out, and the catalog does not offer it, listed or hidden, at any client_version I tried from 0.50.0 through 0.166.0.
What changed in d2c486f.
One question. Where did the order and gpt-5.5 in the review come from? |
TheGreatAxios
left a comment
There was a problem hiding this comment.
The built-in ChatGPT model list drops gpt-5.4, gpt-5.4-mini, and gpt-5.5, defaults to gpt-6.1-sol, and sets each model's reasoning-effort ceiling to the served catalog. The API-key list and its gpt-5.4 default are unchanged.
No findings.
…live-codex-model-catalog-fetch-for-chatgpt The comment above CODEX_DEFAULT_MODELS conflicted with #1580; this keeps both: the live-catalog fallback role and the Plus-catalog provenance. The list is unchanged.
Summary
GET /codex/modelsreturned for a ChatGPT Plus account. Availability varies by plan and rollout, so this is a fallback, not what every account can select. feat(provider): list the models each ChatGPT account serves #1579 replaces it with each account's live list.Verification
bun run checkpasses.GET /codex/models(client_version 0.165.0, ChatGPT Plus, 2026-11-01) lists the same models in the same order, with these levels, and does not include gpt-5.5. The order is the same from client_version 0.160.0 through 0.166.0.Part of CL-11727