Repository navigation
Support admitted OPENAI error caused increased rate limit consumption - zero help #14628
Closed as duplicate
Description
What version of the IDE extension are you using?
v26.311.21342
What subscription do you have?
Plus
Which IDE are you using?
Cursor
What platform is your computer?
No response
What issue are you seeing?
Rate limit consumption dramatically accelerated due to issue on the side of OpenAI. Weekly limit hit in just a few messages. Support admitted that my Codex rate limit consumption "did not match actual usage" and was a "metering issue" but then said they did "not have the ability" to make amends for THEIR error.
Absolutely ridiculous.
What steps can reproduce the bug?
Use Codex via IDE extension for a few messages of work. Watch rate limit magically disappear.
What is the expected behavior?
Accurate usage metering that will enable me to use Codex for a reasonable amount of usage before hitting weekly limits.
Additional information
No response
Activity
github-actions commentedon Mar 13, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Chavezrene commentedon Mar 13, 2026
Not a duplicate, support confirmed my issue.
tibo-openai commentedon Mar 13, 2026
When was this and do you have a session id?
nishikawa7863 commentedon Mar 14, 2026
@tibo-openai This is being widely reported in #14593, where multiple Pro, Plus, and Business users are confirming the same accelerated drain over the past few days.
sibonyves commentedon Mar 14, 2026
I was the original poster on #13568. Below a screenshot of my usage page.
I've been using exclusively codex 5.3 xhigh like always since it came out. On march 5 when you announced fixing a bug with 2X not applying to everyone, 2X stopped applying to me (or something else happened but it feels like usage dropped about twice as fast). No fancy 5.4 (wasn't out), no websockets (don't know what it means), no /fast (it's already fast enough). I do very (very) long sessions but I've always done that.
My issue was closed but it is definitely not solved.
User ID: user-WO80XRMuQXS5ncJJ6FLJ2Zlp
Current session ID: 019cd699-36de-7433-991b-fb250d769bae
etraut-openai commentedon Mar 27, 2026
We're tracking this issue in #14593.