Skip to content

"You've hit your usage limit." Despite 10% Rate Limit Usage Remaining #12299

Open
Open
"You've hit your usage limit." Despite 10% Rate Limit Usage Remaining#12299
Labels
bugSomething isn't workingextensionIssues related to the VS Code extensionrate-limitsIssues related to rate limits, quotas, and token usage reporting

Description

@justinTM
justinTM
opened on Feb 20, 2026

What version of the IDE extension are you using?

0.4.76

What subscription do you have?

Plus

Which IDE are you using?

VS Code

What platform is your computer?

Linux 6.1.129-138.220.amzn2023.x86_64 x86_64 x86_64

What issue are you seeing?

I've been rationing my weekly limit (Codex is way more efficient at tokens than Claude, nice job) using Codex-5.3, and I just ran into a new issue I haven't seen before:

At 10% remaining, I keep getting this message from all models:

You've hit your usage limit. Upgrade to Pro (https://chatgpt.com/explore/pro), visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at Feb 23rd, 2026 9:01 PM.

What steps can reproduce the bug?

Use 90% of your weekly usage, then try to prompt Codex

What is the expected behavior?

I get booted out at 0.1%, not 10%

Additional information

Image

Activity

  1. justinTM
    added
    extensionIssues related to the VS Code extension
    on Feb 20, 2026
  2. github-actions
    added
    bugSomething isn't working
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Feb 20, 2026

  3. github-actions commented on Feb 20, 2026

    @github-actions
    github-actionsBot
    on Feb 20, 2026 – with GitHub Actions
    Contributor

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

    Powered by Codex Action

  4. justinTM commented on Feb 20, 2026

    @justinTM
    justinTM
    on Feb 20, 2026
    Author

    Thread ID:

    9888a61d-81e0-44b2-97a5-e20f782f112d

  5. TJZine commented on Feb 20, 2026

    @TJZine
    TJZine
    on Feb 20, 2026

    same issue here. have 21% remaining when opening a new session in codex CLI and the website usage page shows 21% but when i try to send any message it get the usage limits message.

    Thread ID: 019c7a95-753c-7df2-9c77-3d122f357ef4

  6. etraut-openai commented on Feb 20, 2026

    @etraut-openai
    etraut-openai
    on Feb 20, 2026
    Contributor

    @justinTM, I can't find your thread ID in our database. Did you use /feedback to upload the logs and session details? If so, it appears it didn't upload successfully. If you're able to repro in a new session, please use /feedback to upload the logs and session details and post the thread ID here.

    @TJZine, I see your thread ID in our database. I quickly looked at your logs. I'm guessing that you're using the experimental subagents feature? Have you overridden the default value of agents.max_threads in your config? You triggered a 429 (Too Many Requests) error from our service, which can happen if you set max_threads beyond the default value.

  7. TJZine commented on Feb 20, 2026

    @TJZine
    TJZine
    on Feb 20, 2026

    @etraut-openai I do have multi_agent feature set to true in the config but no other settings related to it like agents.max_threads. I just tried setting multi_agent to false but I still get the same usage error trying a test message again in a fresh chat.

  8. jif-oai commented on Feb 20, 2026

    @jif-oai
    jif-oai
    on Feb 20, 2026
    Contributor

    Can you /feedback and share the contents of your config.toml files?

  9. TJZine commented on Feb 20, 2026

    @TJZine
    TJZine
    on Feb 20, 2026

    okay submitted through feedback, and pasted my current config with the bug report. New thread ID: 019c7ca0-4561-7f43-b66c-a24d2cdc2a10

  10. etraut-openai commented on Feb 20, 2026

    @etraut-openai
    etraut-openai
    on Feb 20, 2026
    Contributor

    @TJZine, the logs show that you are at 0% remaining for your weekly utilization. Where are you seeing that you have 10% remaining? Is that appearing in the app?

  11. TJZine commented on Feb 20, 2026

    @TJZine
    TJZine
    on Feb 20, 2026

    @etraut-openai I see 21% remaining on the usage webpage as seen here.

    Image

    I also see it when opening a new chat in codex and using /status

    Image

    But when I send anything and run status again it then shows 0%

    Image

    Not sure exactly whats going on but I should have the 21% left based on my monitoring on my weekly usage and a 20% drop is pretty big/noticeable especially with the 2x limits.

  12. justinTM commented on Feb 22, 2026

    @justinTM
    justinTM
    on Feb 22, 2026
    Author

    @etraut-openai thanks for your reply -- just re-uploaded. ID:

    ef7e20d7-5c56-48eb-b3eb-ec63fcedf674

    contents of ~/.codex/config.toml:

    model = "gpt-5.1-codex-mini"
model_reasoning_effort = "medium"
personality = "pragmatic"

[features]
shell_snapshot = true

[projects."/home/ec2-user"]
trust_level = "trusted"

    @justinTM, I can't find your thread ID in our database. Did you use /feedback to upload the logs and session details? If so, it appears it didn't upload successfully. If you're able to repro in a new session, please use /feedback to upload the logs and session details and post the thread ID here.

    @TJZine, I see your thread ID in our database. I quickly looked at your logs. I'm guessing that you're using the experimental subagents feature? Have you overridden the default value of agents.max_threads in your config? You triggered a 429 (Too Many Requests) error from our service, which can happen if you set max_threads beyond the default value.

  13. flier268 commented on Feb 24, 2026

    @flier268
    flier268
    on Feb 24, 2026
    Image Thread ID: 019c8e22-5627-79d1-8298-8c02db63d788

  14. limtaewon commented on Feb 24, 2026

    @limtaewon
    limtaewon
    on Feb 24, 2026

    Additional debug info:

    Thread ID: 019c8f92-d2c3-7ee3-9cd5-d050276b22a6

    Feedback has been uploaded via /feedback.

    Repro:

    • /status shows included quota remaining (38% weekly)
    • codex exec "Say pong" -> usage limit error
    • codex exec --model gpt-5.3-codex-spark -> works
    • Same account works on another machine

    This appears to be quota bucket misrouting specific to this device/session.

  15. mpaghubasan commented on Apr 30, 2026

    @mpaghubasan
    mpaghubasan
    on Apr 30, 2026

    same issue. ID: 019ddcd1-396a-77f1-94a6-47a14518ae5b

    /Status result:

    Image

  16. OilRabbit commented on Apr 30, 2026

    @OilRabbit
    OilRabbit
    on Apr 30, 2026

    Hi. Same here. Thread ID:
    019dd506-40c6-78c1-a33c-5f620d51ec23
    Thanks

  17. iqdoctor commented on May 31, 2026

    @iqdoctor
    iqdoctor
    on May 31, 2026
    ╭─────────────────────────────────────────────────────────╮
│ >_ OpenAI Codex (v0.135.0)                              │
│                                                         │
│ model:       gpt-5.3-codex xhigh   /model to change     │
│ directory:   /home/…/launch-fix-autopolot-observation-5 │
│ permissions: YOLO mode                                  │
╰─────────────────────────────────────────────────────────╯

  Tip: New Use /fast to enable our fastest inference with increased plan usage.

/status

╭────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│  >_ OpenAI Codex (v0.135.0)                                                                            │
│                                                                                                        │
│ Visit https://chatgpt.com/codex/settings/usage for up-to-date                                          │
│ information on rate limits and credits                                                                 │
│                                                                                                        │
│  Model:                       gpt-5.3-codex (reasoning xhigh, summaries auto)                          │
│  Directory:                   /home/tools/oh-my-codex.omx-worktrees/launch-fix-autopolot-observation-5 │
│  Permissions:                 Full Access                                                              │
│  Agents.md:                   <none>                                                                   │
│  Account:                     commonvibe@protonmail.com (Pro Lite)                                     │
│  Collaboration mode:          Default                                                                  │
│  Session:                     019e7d7d-2190-74d3-b76f-7f39dfdf64eb                                     │
│                                                                                                        │
│  Context window:              100% left (0 used / 250K)                                                │
│  5h limit:                    [███████████████████░] 94% left (resets 13:26)                           │
│  Weekly limit:                [░░░░░░░░░░░░░░░░░░░░] 0% left (resets 13:36)                            │
│  GPT-5.3-Codex-Spark limit:                                                                            │
│  5h limit:                    [████████████████████] 100% left (resets 18:03)                          │
│  Weekly limit:                [█████████████░░░░░░░] 66% left (resets 16:49 on 4 Jun)                  │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────╯


› ping


⚠ Skill descriptions were shortened to fit the 2% skills context budget. Codex can still see every skill, but some descriptions are shorter. Disable unused skills or plugins to leave more room for the rest.

• SessionStart hook (completed)
  hook context: [Execution environment]- surface: attached tmux runtime - tmux- omx runtime surfaces: omx team, omx hud, and omx question are directly usable in this session- omx question: visible temporary
  renderer available from the current pane; primary success JSON is answers[]

■ You've hit your usage limit. Visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at 1:36 PM.

    gpt-5.3-codex xhigh · /home/tools/oh-my-codex.omx-worktrees/launch-fix-autopolot-observation-5 · fix/autopolot-observation-5 · Context 100% left · Context 0% used · 250K window · 0 in · 0 out · 5h 94% left 

    ■ You've hit your usage limit. Visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at 1:36 PM.
To continue this session, run codex resume 019e7d7d-2190-74d3-b76f-7f39dfdf64eb

  18. tanjim750 commented on Jun 5, 2026

    @tanjim750
    tanjim750
    on Jun 5, 2026

    I'm experiencing the same issue with a ChatGPT Plus account.

    Details:

    • Active ChatGPT Plus subscription (auto-renewal date is visible in billing settings).
    • Codex usage page is accessible and shows available quota (5h limit with ~99% remaining).
    • Codex is available in my account.
    • However, when attempting to use Codex, I receive the following error:

    "The 'gpt-5.3-codex' model is not supported when using Codex with a ChatGPT account."

    This does not appear to be a quota or subscription issue, since usage limits are still available. It seems like an account entitlement, model mapping, or backend synchronization problem.

    Has anyone found a workaround, or can the team confirm whether this is a known issue affecting ChatGPT Plus users?

  19. leon0399 commented on Jun 5, 2026

    @leon0399
    leon0399
    on Jun 5, 2026
    ■ You've hit your usage limit. Upgrade to Pro (https://chatgpt.com/explore/pro), visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at 4:01 AM.

/status

╭─────────────────────────────────────────────────────────────────────────────────────────╮
│  >_ OpenAI Codex (v0.137.0)                                                             │
│                                                                                         │
│ Visit https://chatgpt.com/codex/settings/usage for up-to-date                           │
│ information on rate limits and credits                                                  │
│                                                                                         │
│  Model:                       gpt-5.5 (reasoning medium, summaries detailed)            │
│  Permissions:                 Workspace (Approve for me)                                │
│  Collaboration mode:          Default                                                   │
│  Session:                     019e9990-4c2b-77a2-b9da-9a86d1a06064                      │
│                                                                                         │
│  Context window:              30% left (185K used / 258K)                               │
│  5h limit:                    [███████████████░░░░░] 76% left (resets 04:01)            │
│  Weekly limit:                [███████████████████░] 96% left (resets 23:01 on 12 Jun)  │
│  GPT-5.3-Codex-Spark limit:                                                             │
│  5h limit:                    [████████████████████] 100% left (resets 05:24)           │
│  Weekly limit:                [████████████████████] 100% left (resets 00:24 on 13 Jun) │
│  premium limit:                                                                         │
╰─────────────────────────────────────────────────────────────────────────────────────────╯

  20. septagram commented on Jun 7, 2026

    @septagram
    septagram
    on Jun 7, 2026
    Image

    ...and it is 1:58 a.m. so the date it wants me to wait for is in the past.

    I've just purchased my sub BTW.

    Session ID: 019ea375-8696-7462-ae1c-04fbe5b702eb

  21. andreasskeidsvoll commented on Jun 15, 2026

    @andreasskeidsvoll
    andreasskeidsvoll
    on Jun 15, 2026

    Same problem here, encountered today at 3% remaining with a Plus subscription. Session ID 019ecadb-94a8-7c42-87fc-e8bbc536d99d.

    Image

    EDIT: sending a message with /feedback as the only content in the Codex app (MacOS, version 26.609.41114) actually successfully triggered the prompt that had failed multiple times earlier (also after reopening the app multiple times and double-checking my remaining usage), and made it run to completion.

  22. skye1349 commented on Jun 19, 2026

    @skye1349
    skye1349
    on Jun 19, 2026

    Same here, I just purchase the sub.
    100% left but hit the usage limit already.
    session ID: 019e7c59-b56f-74d0-aa3c-a5474aca31da

    Image

  23. dvdmchl commented on Jun 20, 2026

    @dvdmchl
    dvdmchl
    on Jun 20, 2026 – with ChatGPT Codex Connector

    I hit a very similar issue after upgrading from Plus to Pro Lite.

    Symptoms:

    • Codex CLI /status showed Account: Pro Lite.
    • /status showed remaining quota, e.g. 80% 5h limit and 97% weekly limit.
    • Any prompt still failed with:
      You've hit your usage limit. Upgrade to Pro ... or try again at ...
    • The issue persisted in the same session after the plan upgrade.
    • gpt-5.3-codex-spark also appeared in /status with 100% quota, but selecting it failed with:
      The 'gpt-5.3-codex-spark' model is not supported when using Codex with a ChatGPT account.

    Fix that worked:

    • codex logout
    • renamed %USERPROFILE%\.codex to .codex_BACKUP
    • ran codex login again
    • started a fresh Codex session with gpt-5.5

    After recreating the local .codex directory, gpt-5.5 prompts worked again.

    This suggests stale local Codex state after a Plus -> Pro Lite upgrade can cause false usage-limit failures even when /status and the usage dashboard show available quota.

  24. NoComplyDev commented on Jun 20, 2026

    @NoComplyDev
    NoComplyDev
    on Jun 20, 2026

    Same here. Absolutely ridiculous. Used /feedback multiple times. I've paid for a service and it isn't being provided.

    Feedback ID 019ed59b-8545-7473-b21e-dc463408ca46

  25. f1bzz commented on Jun 21, 2026

    @f1bzz
    f1bzz
    on Jun 21, 2026

    Same, just bought pro version and I am rate-limtied now. used limit reset, now +3 days to rate limit 🫤
    feedback id 019ee944-fc2a-7740-a8d5-7336a790000b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingextensionIssues related to the VS Code extensionrate-limitsIssues related to rate limits, quotas, and token usage reporting

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions