Codex model picker compatibility and slug fixes
Cluster 23097 · agent/secret sources. Data as of
1 open item. Fix merged in #115760 on 19 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #115760. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These issues and PRs center on problems with model name validity, filtering, and selection in the Codex/OpenAI-Codex provider, particularly around which model slugs are accepted or rejected by ChatGPT accounts versus Codex backends. Several entries address adding, removing, or correcting specific model identifiers like gpt-5.3-codex-spark and pro-tier slugs that return HTTP 400 errors.
Open issues0
Open PRs1
- PR#23189fix(codex): trust live ChatGPT picker catalog
Fixes on record
-
#115760 fix(agent): Codex pool rotates to the next account on a ChatGPT-account model entitlement 400 (#71970, salvage #71973)
files:
agent/agent_runtime_helpers.py,agent/credential_pool.py,agent/credential_pool_model_cooldowns.py,agent/error_classifier.py,agent/fallback_cooldown.py,contributors/emails/[redacted:email],tests/agent/test_codex_model_entitlement_rotation.py,tests/agent/test_entitlement_fail_closed.py,tests/agent/test_error_classifier.py,website/docs/user-guide/features/credential-pools.md
3 PRs closed without merging
From the close comments: duplicate 1 · merged via another change 1 · superseded by another PR 1
-
#23175 fix(cli): drop ChatGPT-account-rejected models from openai-codex picker · superseded by another PR →
#23189 -
#61665 fix(codex): drop unsupported pro defaults · duplicate →
#89194 -
#71973 fix(agent): rotate Codex credentials on model entitlement rejection · merged via another change →
f07afac,#115760,#71970,#71973
Closed issues · 2
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.26: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent/secret sources
- Merged PRs
- #115760
- Closed issues
- 2
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 19 Sep 2026