Skip to content

Hitting rate limits #6172

Closed
Closed

Description

@iSuslov

I'm aware this isn't the right place to file this issue, BUT it's now clear that a huge cut in limits is being observed. Reddit is talking about it, and your GitHub is full of similar issues. This is being systematically observed by many independent users. We have reached a point where we can look around and confirm it - we are not imagining things. And we observe silence from your end.

Is it the new standard among AI companies to serve a downgraded product and cut limits after a few month?

Thread update: ae-openai clarified that limits weren't reduced. However, a cache issue was identified which caused cache misses and huge usage spikes, with the expected fix shipped today (Nov 4).

Update 2: Today, Nov 5 usage was reset.

Activity

  1. github-actions commented on Nov 3, 2025

    @github-actions
    Contributor
  2. added
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Nov 3, 2025
  3. ae-openai commented on Nov 4, 2025

    @ae-openai
    Contributor

    Hey,

    • We haven't reduced local limits in any way. If you're seeing lower usage, please flag it as it's a bug. On that note, we have identified one issue causing increased cache misses which are consuming limits much more quickly. Fix should be out tomorrow.
    • For cloud (aka web), we are working to enable those limits to go much further. We just shipped our first improvement tonight: Failed cloud tasks will no longer count against limits. (We should have caught this earlier.) Many more improvements coming.
  4. lunamidori5 commented on Nov 4, 2025

    @lunamidori5
    • For cloud (aka web), we are working to enable those limits to go much further. We just shipped our first improvement tonight: Failed cloud tasks will no longer count against limits. (We should have caught this earlier.) Many more improvements coming.

    Thank you! On top of that I hope those poorly formatted messages that crash the full cloud website also do not count... Thank y'all for your hard work!

  5. iSuslov commented on Nov 4, 2025

    @iSuslov
    Author

    Hey @ae-openai, this is my particular case:

    Image

    It says limits will reset on Nov 9th, thus it started on Nov 2th and by using it for one day (two 5 hour windows) I've got 80% of my weekly limit reached. You guys should announce this caching issue publicly and reset weekly limits of those who was affected.

  6. techjoec commented on Nov 4, 2025

    @techjoec

    Reposting some data here as #6008 (comment) (@etraut-openai ) noted this thread is an "update". Issue I put data into on Saturday post "fix": #6008

    Summary

    Plan: PRO
    Duration to weekly limit hit: Under 24 hours!
    Usage "week" started: 11/2/2025 12:10:00 AM UTC.

    My week

    I ran my numbers for CLI and cloud from the start of my "week" til I was prevented from using the service and this is what I came up with. Might be off a slight hair but likely very close to actuals..

    Cloud Totals
    CloudTasks: 109
    Tokens: 3891767
    Total Task Hours: 20.25

    Cloud Task Averages
    Tokens per task: 35704
    Minutes per task: 11

    CLI Session Totals
    InputCachedTokens - 352834688
    InputTokens - 375819446
    OutputTokens - 2073269
    ReasoningTokens - 1042304

    Five-hour usage window sample

    As for 5 hour usage...The below activity (and the CLI is only end of session stats, and some were likely started before that current 5-hour window reset so likely a bit inflated!

    Cloud Totals
    CloudTasks: 29
    Tokens: 1075448
    Total Task Hours: 5.38

    Cloud Task Averages
    Tokens per task: 37084
    Minutes per task: 11

    CLI Session Totals
    InputCachedTokens - 90468224
    InputTokens - 96415999
    OutputTokens - 653123
    ReasoningTokens - 351552

    Serena MCP is the only extra tool I use, and Codex CLI makes sure to forget about it for 99% of the session anyway.

    Overall 5 hour span of usage

    timestamp source primary secondary InputTokens InputCachedTokens OutputTokens ReasoningTokens assistant_turn_tokens duration_minutes diff_adds diff_removes
    2025-11-02T00:02:12.57Z CLI 0 11 10301592 9392512 82209 33088
    2025-11-02T00:08:10.199Z CLI 1 11 165130 140160 5538 4224
    2025-11-02T00:09:06.164Z CLI 1 12 216218 167552 8636 6720
    2025-11-02T00:09:55.806Z CLI 2 12 11143894 10085888 94728 39040
    2025-11-02T00:17:29.111Z CLI 3 12 849279 724608 11920 6656
    2025-11-02T00:19:45.013Z CLI 4 12 16552345 14958976 108591 44096
    2025-11-02T00:20:26.739Z CLI 5 12 1574876 1427200 20049 8384
    2025-11-02T00:20:28Z CLOUD 26283 7 279 92
    2025-11-02T00:21:33.769Z CLI 5 13 18241249 16472448 112098 45696
    2025-11-02T00:24:35Z CLOUD 32075 9 542 542
    2025-11-02T00:28:16.486Z CLI 6 13 22166415 20332672 123165 50304
    2025-11-02T00:30:21Z CLOUD 56573 18 367 184
    2025-11-02T00:31:04.325Z CLI 7 13 23844089 21805952 128001 52480
    2025-11-02T00:36:40Z CLOUD 46140 10 1062 6
    2025-11-02T00:50:15Z CLOUD 126616 26 927 31
    2025-11-02T01:03:04.502Z CLI 8 13 4172315 3762432 60647 35264
    2025-11-02T01:09:16.943Z CLI 8 14 24411605 22370176 129541 53184
    2025-11-02T01:17:35.241Z CLI 11 3 7467843 6985216 87521 50496
    2025-11-02T01:20:19Z CLOUD 59472 14 837 108
    2025-11-02T01:21:38.957Z CLI 12 3 8586939 8084608 95488 54080
    2025-11-02T01:30:50.153Z CLI 12 4 8930397 8315776 103363 59008
    2025-11-02T01:35:16Z CLOUD 47974 12 1226 20
    2025-11-02T01:36:18.228Z CLI 17 5 10658080 9909120 116252 65792
    2025-11-02T01:37:31.099Z CLI 18 5 11331541 10577664 121280 68224
    2025-11-02T01:38:56.01Z CLI 18 6 11727535 10959488 125171 70848
    2025-11-02T01:47:04.227Z CLI 19 6 13697296 12771584 140823 77632
    2025-11-02T01:48:41.797Z CLI 22 7 13697296 12771584 140823 77632
    2025-11-02T01:50:24Z CLOUD 41994 9 907 74
    2025-11-02T01:54:10Z CLOUD 10656 10 68 5
    2025-11-02T01:58:21.991Z CLI 23 7 15007732 14055296 164822 99520
    2025-11-02T02:00:25Z CLOUD 89546 22 1482 27
    2025-11-02T02:04:02.047Z CLI 28 9 15305937 14351488 169008 103168
    2025-11-02T02:06:15Z CLOUD 18869 9 183 14
    2025-11-02T02:14:29.01Z CLI 29 9 57367 37888 754 512
    2025-11-02T02:16:04.433Z CLI 32 9 18085223 17096064 185383 110272
    2025-11-02T02:16:26.43Z CLI 32 10 687054 573440 6163 3968
    2025-11-02T02:18:49Z CLOUD 12103 9 103 22
    2025-11-02T02:20:37.583Z CLI 33 10 2896820 2571136 16893 10176
    2025-11-02T02:25:22Z CLOUD 71519 20 901 43
    2025-11-02T02:30:25.715Z CLI 45 14 19385592 18358272 192675 113984
    2025-11-02T02:30:59Z CLOUD 41871 10 254 5
    2025-11-02T02:31:05.065Z CLI 46 14 20036967 19006592 194727 114112
    2025-11-02T02:43:06Z CLOUD 29800 13 148 6
    2025-11-02T02:43:11.204Z CLI 49 15 20701246 19655296 199937 116672
    2025-11-02T02:46:24.807Z CLI 56 17 21391911 20331264 204662 119232
    2025-11-02T02:50:19Z CLOUD 42321 10 566 16
    2025-11-02T02:52:48.35Z CLI 57 17 22814134 21563136 210774 122112
    2025-11-02T03:00:35Z CLOUD 15494 7 81 7
    2025-11-02T03:00:50.215Z CLI 63 19 24473416 23202048 220054 125696
    2025-11-02T03:01:48.331Z CLI 66 20 24473416 23202048 220054 125696
    2025-11-02T03:05:28Z CLOUD 36797 10 291 39
    2025-11-02T03:11:32.052Z CLI 69 21 25981713 24701184 226658 128832
    2025-11-02T03:12:47Z CLOUD 17178 9 267 10
    2025-11-02T03:20:17Z CLOUD 34360 8 235 10
    2025-11-02T03:24:51Z CLOUD 35604 18 106 25
    2025-11-02T03:29:46.233Z CLI 78 23 26753057 25467008 228396 129216
    2025-11-02T03:30:16Z CLOUD 40582 11 5928 12
    2025-11-02T03:38:08Z CLOUD 16313 6 258 0
    2025-11-02T03:43:13Z CLOUD 36926 16 198 24
    2025-11-02T03:45:11Z CLOUD 21209 5 473 23
    2025-11-02T03:48:55.153Z CLI 95 29 9546 0 71 64
    2025-11-02T03:50:19Z CLOUD 28764 8 542 34
    2025-11-02T03:52:47Z CLOUD 0
    2025-11-02T03:54:16Z CLOUD 35176 16 209 0
    2025-11-02T03:54:56Z CLOUD 3233 1 7 1
    2025-11-02T04:10:04.832Z CLI 100 30

    Daily usage from OpenAI directly

    Unsure if https://chatgpt.com/backend-api/wham/usage/credit-usage-events reports "date" in UTC or not...But if it does, then the first day can be fully ignored. But it doesn't even add up to 100%...Confusing.

    {
    "date": "2025-11-01",
    "product_surface_usage_values": {
    "cli": 4.734244660872603,
    "web": 19.14151781164927,
    "github_turn": 0.06114338122898196,
    "github_code_review": 0.7460948304726966
    }
    }

    {
      "date": "2025-11-02",
      "product_surface_usage_values": {
        **"cli": 5.380617548150413,**
        **"web": 39.7206329795752,**
      }
    },
    

    Soooooooooooooo

    @etraut-openai This is "working as intended"? Please advise ASAP.

    The site says:
    Pro Usage: Usage limits apply across both local and cloud tasks. Average users can send 300-1,500 local messages every 5 hours or 50-400 cloud tasks every 5 hours, with a shared weekly limit.

    That is really not the case here it seems.

  7. msbealo commented on Nov 4, 2025

    @msbealo

    I'm not a fancy CLI user, but I have been using the web interface for some projects. However, on Thursday, the 30th, I was hit by this issue. I was suddenly rate-limited, significantly below my previous usage. I struggled on for a few days using a local environment in VS Code, but it didn't help much. My 5-hour limit was being reached after 2-3 prompts. Now my weekly limit has been reached, and I have to wait 5 more days!

    In the meantime, I've been investigating alternatives, but this has significantly affected my progress.

    Image
  8. pontes-a7 commented on Nov 4, 2025

    @pontes-a7

    any update? @ae-openai

  9. techjoec commented on Nov 4, 2025

    @techjoec

    The only update I've seen is that they will stop charging us for when Cloud fails. That should be a no-brainer and should have already been in place before billing us, but that aside there's something seriously wrong OR the dozens/hundreds of us complaining (see OpenAI's discussion boards, reddit.com/r/codex/, here, etc) are either stupid or crazy (tell us which, please). I've spent (wasted) hours providing numbers and many others have too. OAI seems to feel this is working as intended apparently.

    These comments here are frustrating: https://old.reddit.com/user/embirico especially "web tasks are longer". Uhhh..I average 11 minutes overall. ~100 cloud tasks and ~22mil non-cached tokens from CLI ate 100% of my Pro weekly limit!?!?

    As for CLI usage, this is a recent dump I did of the token usage. I haven't really changed my habits at all, in fact have done things to try to streamline, but apply_patch and sed taking up such a gigantic share of the token load, and often on the same damn files over and over, surely is not helping. It feels like after making such a gigantic usage-impacting change with sudden jerk-of-the-wheel motions that slow-rolling tiny "improvements" now really isn't helping one bit here.

    Function call type Calls Total tokens Share of total Avg tokens per call
    shell 1,315 302,839,198 88.86 % ≈230,296
    mcp__serena__write_memory 26 8,277,500 2.43 % 318,365
    update_plan 60 7,582,367 2.22 % 126,373
    mcp__serena__search_for_pattern 51 5,612,423 1.65 % 110,048
    mcp__serena__read_memory 42 4,086,937 1.20 % 97,308
    mcp__serena__think_about_whether_you_are_done 11 2,875,806 0.84 % 261,437
    mcp__serena__find_symbol 14 1,486,131 0.44 % 106,152
    mcp__serena__summarize_changes 3 1,046,374 0.31 % 348,791
    mcp__serena__think_about_task_adherence 4 939,356 0.28 % 234,839
    mcp__serena__list_dir 16 894,987 0.26 % 55,937
    mcp__serena__get_current_config 4 868,927 0.25 % 217,232
    mcp__serena__think_about_collected_information 6 749,603 0.22 % 124,934
    mcp__serena__check_onboarding_performed 11 708,449 0.21 % 64,404
    mcp__serena__find_file 8 564,971 0.17 % 70,621
    mcp__serena__initial_instructions 5 530,192 0.16 % 106,038
    mcp__serena__list_memories 3 438,866 0.13 % 146,289
    mcp__serena__activate_project 13 382,333 0.11 % 29,410
    mcp__serena__switch_modes 8 381,639 0.11 % 47,705
    mcp__serena__get_symbols_overview 3 294,828 0.09 % 98,276
    read_mcp_resource 3 80,636 0.02 % 26,879
    list_mcp_resources 2 72,177 0.02 % 36,089
    list_mcp_resource_templates 1 50,198 0.01 % 50,198
    mcp__serena__onboarding 1 39,656 0.01 % 39,656
    Other / Unassigned — 12,802 0.00 % —
    Command Calls Total tokens Share of shell tokens Avg tokens/call
    apply_patch 250 78,625,822 26.00 % ≈314,503
    sed 239 43,584,953 14.41 % 182,363
    lua 114 38,096,266 12.60 % 334,177
    rg (ripgrep) 144 24,911,137 8.24 % 172,994
    ******** 95 24,834,789 8.21 % 261,418
    python3 40 15,988,559 5.29 % 399,713
    git 57 9,117,436 3.02 % 159,955
    ls 69 8,844,375 2.92 % 128,179
    nl 55 8,468,044 2.80 % 153,964
    pnpm 29 6,715,358 2.22 % 231,564
    luacheck 23 6,227,061 2.06 % 270,741
    applypatch 23 5,437,445 1.80 % 236,410
    python 22 5,112,512 1.69 % 232,386
    cat 30 4,911,715 1.62 % 163,723
    jq 18 2,287,776 0.76 % 127,098
    make_package.sh 4 2,166,519 0.72 % 541,629
    set 10 1,501,474 0.50 % 150,147
    gh 3 1,455,285 0.48 % 485,095
    find 11 1,418,196 0.47 % 128,926
    rm 6 1,384,068 0.46 % 230,678
    mkdir 5 1,351,405 0.45 % 270,281
    lynx 7 1,203,903 0.40 % 171,986
    chmod 3 940,198 0.31 % 313,399
    luac 5 915,651 0.30 % 183,130
    bundle=/tmp/task_bundle.json; 8 855,772 0.28 % 106,971
    echo 5 794,555 0.26 % 158,911
    head 5 769,247 0.25 % 153,849
    wc 4 589,987 0.20 % 147,496
    unzip 5 585,306 0.19 % 117,061
    printf 3 519,334 0.17 % 173,111
    grep 5 465,364 0.15 % 93,072
    awk 2 387,552 0.13 % 193,776
    for 2 379,284 0.13 % 189,642
    rmdir 1 372,822 0.12 % 372,822
    timeout_ms 1 366,519 0.12 % 366,519
    timeout 2 181,203 0.06 % 90,601
    bash 1 130,110 0.04 % 130,110
    tmpdir=$(mktemp) 1 83,302 0.03 % 83,302
    printenv 1 61,054 0.02 % 61,054
    UA="Mozilla/5.0 1 60,877 0.02 % 60,877
    TOKEN=$(jq 1 56,533 0.02 % 56,533
    curl 2 47,648 0.02 % 23,824
    which 1 28,485 0.01 % 28,485

    I hate being a whiner, but at $200/month having my entire weekly quota blown in under 24 hours is absolutely bonkers and not aligned with the stated plan limits from what I can tell. And my usage is hobby strictly, OAI is banned and CIDR blocked at work for Reasons(tm). I feel for the folks getting jammed with this that rely on it for their day jobs!

    Image

    Also this one is gold right here: #6198 Poor guy had codex change one line and lost 8% of his Plus budget. Yeah, tell us how that is "working correctly" please??

  10. techjoec commented on Nov 4, 2025

    @techjoec

    And to add, the messaging from OAI is borderline sloppy. Saw a few tweets today now that "in the next two weeks" things might improve. Then nuggets like this:

    Image

    So which is it, team? Are us users stupid/crazy, or is the platform broken??

  11. techjoec commented on Nov 5, 2025

    @techjoec

    Ah well. Canceled my Pro. Guess that's all I can do. Best of luck to all and I hope they fix things. :(

    The interesting part of it is that I tried to get the "AI Support" to open a ticket for me before doing this, but it insisted that my usage is advanced and suggested I pay more for credits. After a half dozen prompts I said "Ok cancel my Pro" and without any hesitation it fully canceled my plan. No confirmations or anything...ha! I was going to keep Plus for a month, but the kick in the butt was clear!

    You said:
    Ok cancel my Pro

    The assistant said:
    You have been granted a prorated refund based on your usage. Your active subscription has been cancelled. The refund will show up in your bank statement within 10 days.

  12. marked Web vs CLI quotas #5783 as a duplicate of this issue on Nov 5, 2025
  13. aitikcho commented on Nov 5, 2025

    @aitikcho

    It was a good cloud for coding, however ... today I have tried 3 tasks, all of them failed :
    By the time of these 3 unsuccessful tasks I am 80% of my 5 hour limit and 25% of my 5 day limit. I used to code with this tool and now it seems I will have to use another tool. Hope I get good suggestions.

    I’m sorry, but I’m not able to complete this request.

    why?

    Copy
    I’m not sure why the earlier response said the request couldn’t be completed—there’s nothing in the project setup that prevents working on it. If you’d still like to proceed, let me know and I’ll be happy to help implement the project-specific data handling and dropdown.

  14. msbealo commented on Nov 5, 2025

    @msbealo

    It looks like my usage was reset this evening. I don't know if this has been applied to others, or if it's related to a support ticket I put in a couple of days ago, or what. While I appreciate the reset, I also notice that ONE prompt has used up 17% of my 5-hour usage. It's nice to be back. I certainly haven't got Kilo Code working as well as Codex does on my project, but I hope that this isn't just a temporary fix.

    Image
  15. 46 remaining items

  16. pfahlr commented on Nov 17, 2025

    @pfahlr

    so this is not resolved or still an issue for everyone? Actually I just wanted to sub to the 200 version but now i am hesitant

    don't do it. their support is shit.😑. just go with claude code

    I did go ahead and try claude code, and in quite a few ways it works better, especially enjoying the plugins and ease of adding MCP servers... but the one way it is not better... unfortunately... is this one... wow I burned through my allotment quickly. I just noticed I had 250$ in claude code for web (they've apparently just added a web/cloud environment coding version similar to codex for web) and it expires at midnight nov 18... I think I'll be able to use it all up as I've managed to burn through $60 in credits over the past couple hours.

    It could be the AI companies have decided to work together to price fix... and since all these companies have been able to replace 5-10 engineers with a single engineer running one of these tools, what's 200$ a day when it replaces 5-10 engineers that you had to pay 300-500$/day? It's still a bargain.

    Unfortunately, for many a developer... it's not a bargain for us.

  17. winnal commented on Nov 19, 2025

    @winnal

    From the latest update, the usage limits issue seems to be fixed. Usage is going down way slower now. Even when using the new max model on xhigh effort.

  18. neo-picasso-2112 commented on Nov 20, 2025

    @neo-picasso-2112

    super disappointing. I am actually considering leaving this platform altogether and going open-sourced. What a disappointing rug pull from the OpenAI and Codex team.

  19. rymatoi commented on Nov 21, 2025

    @rymatoi

    @etraut-openai any updates? I don't believe you marked it as a bug 3 weeks ago and it still persists 🤡

  20. rymatoi commented on Nov 21, 2025

    @rymatoi

    @etraut-openai if you can't fix it you can hire me, I'll do it for you

  21. techjoec commented on Nov 22, 2025

    @techjoec

    Asked support very nicely and clearly three times now. Fully ignored for going on 7 days and @etraut-openai and others avoiding this thread completely. Jumping on other minor issues though and linking other issues to this black hole consistently however. Ah well bank charge back and burned some big customers for good. 👋🏼

  22. etraut-openai commented on Nov 22, 2025

    @etraut-openai
    Contributor

    We posted an update on this topic in reddit and X a couple of days ago. Sharing here as well.

    Update on Codex usage

    Over the past weeks, we’ve been working to increase usage limits and fix bugs. Here’s a summary of progress:

    Usage increases since Nov 1

    • Plus and Business users can send >2x more messages on average in the CLI and IDE Extension, and >3x more on Cloud.
    • Pro users can send >1.4x more messages on average in the CLI and IDE Extension, and >2x more on Cloud.
    • Enterprise and Edu plans with flexible pricing continue to offer uncapped usage.
    • How we achieved this:
      • 30% more expected efficiency (and higher intelligence too) with GPT-5-Codex-Max, compared to GPT-5-Codex and GPT-5.1-Codex.
      • 50% rate limits boost for Plus, Business, and Edu. (Priority processing for Pro and Enterprise.)
      • 30% reduction in usage consumption for Cloud tasks specifically.
      • Running multiple versions of a task (aka Best of N) on Codex Cloud is heavily discounted so that it doesn’t blow through your limits.
      • Some other smaller efficiency improvements to the prompt and harness.

    Fixes & improvements

    • You can now buy credits if your ChatGPT subscription is managed via iOS or Google Play.
    • All usage dashboards now show “limits remaining.” Before this change, we saw a decent amount of confusion with the web usage dashboard showing “limits remaining,” whereas the CLI showed “limits used.”
    • Landed optimizations that help you get the same usage throughout the day, irrespective of overall Codex load or how traffic is routed. Before, you could get unlucky and hit a few cache misses in a row, leading to much less usage.
    • Fixed an issue where the CLI showed stale usage information. (You previously had to send a message to get updated usage info.)
    • [In alpha] The CLI shows information about your credit balance in addition to usage limits.
    • [Coming soon] Fixing an issue where, after upgrading your ChatGPT plan, the CLI and IDE Extension showed your old plan.

    Measuring the improvements

    That’s a lot of improvements and fixes! Time to measure the lifts—unfortunately we can’t just look at the daily usage data powering the in-product usage graphs. Due to the multiple rate limit resets as well as changes to the usage limits system to enable credits and increased Plus limits, that daily usage data in the past is not directly comparable.

    So instead we verified how much usage people are getting by looking at production data from this past Monday & Tuesday:

    • Plus users fit 50-600 local messages and 21-86 cloud messages in a 5-hour window.
    • Pro users fit 400-4500 local messages and 141-583 cloud messages in a 5-hour window.
    • These numbers reflect the p25 and p75 of data we saw on Nov 17th & 18th. The data has a long tail so the mean is closer to the lower end of the ranges.

    Bear in mind that these numbers do not reflect the expected 30% efficiency gain from GPT-5.1-Codex-Max, which launched yesterday (Nov 19th). We expect these numbers to improve significantly more!

    Summary

    Codex usage should now be more stable and higher than it was a month ago. Thanks to everyone who helped point out issues—we’ve been investigating them as they come and will continue to do so.

  23. techjoec commented on Nov 22, 2025

    @techjoec

    But tough luck for those of us that didn't get the credits and no comment on support refusing to acknowledge it?

  24. etraut-openai commented on Nov 23, 2025

    @etraut-openai
    Contributor

    Hi @techjoec. Sorry, but I don't have any information about your particular case or your interactions with support. My understanding is that credits were given to users as thanks for their patience as we investigated the issue. Reading through your posts above, it sounds like you had already canceled your subscription by that point.

  25. aaronedev commented on Nov 23, 2025

    @aaronedev

    i think my limits are back to normal level, can anyone confirm the same? I just tested and ran prompts + multiple agents etc. Seems it stabilized itself

  26. techjoec commented on Nov 23, 2025

    @techjoec

    Hi @techjoec. Sorry, but I don't have any information about your particular case or your interactions with support. My understanding is that credits were given to users as thanks for their patience as we investigated the issue. Reading through your posts above, it sounds like you had already canceled your subscription by that point.

    Oh I did, after begging you all for review. I posted extremely detailed logs, examples, and even burned my credits generating them. Full out ignored until after the 'offer' expired. Did you see how I canceled?? I am sure you are busy (no /sarcasm at all) so maybe not but I tried repeatedly to reach out to support via the dang support tool, and it refused to give me a way to make a ticket. So I literally said the below and it just did it....I was actually expecting it to give up on fluff and actually create a support ticket, and I would have stayed Plus at least. This was on Nov 4th, merely hours before you announced on reddit the credit.

    The chat interaction after begging for a support ticket with the support "agent" that canceled my sub Nov 5, 2025, 5:06 AM UTC:

    You said:
    Ok cancel my Pro

    The assistant said:
    You have been granted a prorated refund based on your usage. Your active subscription has been cancelled. The refund will show up in your bank statement within 10 days.

    The specific wording you posted about the credits does not disqualify me. On the Pro plan I used Codex web during the period you stated:

    To thank you for your patience, we’ve granted $200 in free credits to Plus and Pro users who used cloud tasks in the past month, valid until Nov 20.

    I was patient. I posted many times to this issue AND others including verbose stats and log outputs. I begged for clarity and communication as it was impacting us. I got nothing in return. Here we are over two weeks later, and I am being told that the credits were as a thank you for being patient and thus I have no claim to them? I feel I was very patient and eager to help resolve the issue for everyone, tried to provide you and the codex team with data to consider, and was just flat ignored.

    To this date support has ignored my last three emails requesting escalation or even a case number and explicitly denied your claims of any credit offer even exists.

    Support:

    However, there is no official documentation confirming an automatic $200 Codex credit or compensation program associated with this issue.

    :(

  27. etraut-openai commented on Nov 25, 2025

    @etraut-openai
    Contributor

    I'm going to close this issue. There are still a few issues discussed above that we are tracking, but they are covered by other issues:
    #2330
    #6674
    #5999

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 workingcodex-webIssues related to Codex Webrate-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