gpt-5.6-sol' model is not supported and no usage limit #36082

Activity

1. capinfl

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Jul 30, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   rate-limitsIssues related to rate limits, quotas, and token usage reportingIssues related to rate limits, quotas, and token usage reporting

   on Jul 30, 2026
3. github-actions commented on Jul 30, 2026

   

   github-actionsBot

   on Jul 30, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • I am Pro (20x), But Codex shows Pro Lite, and the decrease usage limit speed as like Pro Lite #34918
   • 0.146.0 hides image_generation for Pro accounts until re-login refreshes stale Free plan cache #35923

   Powered by Codex Action
4. D1a0y1bb commented on Aug 1, 2026

   

   D1a0y1bb

   on Aug 1, 2026 – with ChatGPT Codex Connector

   More actions

   I can reproduce this on a renewed ChatGPT Pro ($200 / 20×) subscription.

   Environment

   • Codex CLI: v0.146.0
   • Authentication: ChatGPT account login
   • Subscription: ChatGPT Pro ($200 / 20×), recently renewed after the previous subscription expired
   • Model selected: gpt-5.6-sol

   What happened

   Immediately after renewing the subscription, selecting Sol in Codex CLI returned:

   The 'gpt-5.6-sol' model is not supported when using Codex with a ChatGPT account.
   

   Signing out and signing back in did not fix it. Codex then switched the model from Sol to Terra and rejected the request with a usage-limit error:

   You've hit your usage limit. Add credits to continue, or try again at Aug 8, 2026 11:41.
   

   However, the account still has usage available, and the same ChatGPT account can use gpt-5.6-sol successfully in ChatGPT's web Work mode at the same time.

   Expected behavior

   After a Pro renewal, Codex CLI should recognize the refreshed subscription/model entitlement and remaining usage consistently with ChatGPT Work mode. Logging out and back in should refresh the entitlement if it has become stale.

   This looks like a cross-client entitlement/usage synchronization issue triggered by subscription expiration followed by renewal, rather than an actual usage-limit exhaustion.
5. Jilvert22 commented on Aug 7, 2026

   

   Jilvert22

   on Aug 7, 2026

   More actions

   Same symptom on ChatGPT Pro, reproduced 2026-08-07.

   Environment

   • auth_mode: chatgpt (no API key configured)
   • chatgpt_plan_type = pro, subscription active and not expired
   • Codex CLI: reproduced on both 0.144.1 (Homebrew) and 0.147.0-alpha.6.5 (bundled with the desktop app)

   Symptom

   codex exec -m gpt-5.6-sol → HTTP 400

   The 'gpt-5.6-sol' model is not supported when using Codex with a ChatGPT account.
   

   gpt-5.6-terra and gpt-5.6-luna succeed with the exact same command, auth and config.
   The model name is already the variant form, so this is not the plain gpt-5.6 case.

   Ruled out (each reproduced the identical 400):

   • Ran with no local config at all (moved ~/.codex/config.toml and ~/.codex/models.json aside)
   • Re-authenticated from scratch (sign out / sign in, fresh id_token)
   • Both CLI versions above
   • No project-level .codex/config.toml present

   Inconsistency worth noting: ~/.codex/models_cache.json, re-fetched minutes earlier under this
   same ChatGPT auth, lists gpt-5.6-sol with visibility: "list" and supported_in_api: true.
   The model-listing API advertises Sol for this account while the execution API rejects it.

   As in the original report, this account was upgraded to Pro shortly before the first failure,
   which points at entitlement propagation rather than anything client-side.

   👍React with 👍1Reacted by Ben Elgar
6. basvandaalen commented on Aug 8, 2026

   

   basvandaalen

   on Aug 8, 2026

   More actions

   Same issue.

   👍React with 👍2Reacted by Ben Elgar and Samuel Martinenghi
7. shiyi2499-create commented on Aug 17, 2026

   

   shiyi2499-create

   on Aug 17, 2026

   More actions

   Same issue，how to resolve it？
8. Hai-San commented on Sep 24, 2026

   

   Hai-San

   on Sep 24, 2026

   More actions

   Same issue.