u/AppropriateRanger401

Every since the last reset, OpenAI has decreased limits SIGNIFICANTLY. I am not another one of those saying that I feel like limits are too low. I have proof too, and if other people can post graphs like these on X, it can make an impact on OpenAI. My Nerf Tracking app shows that since the last reset from 3-4 days ago, limits have been halved, from an API value of the previous $160 to the value of $80 of a weekly limit. After the reset, in the first 2 days they nerfed limits by 40% to see if anybody noticed. Since not many people made noise, they decreased usage by a further 10% at the point where it has now become a 50% limit of what it was 4 days ago. Which you can also say means, that now a 2 weeks limit on the plus plan gives you as much usage as what the same plan, which you paid the same amount of money before too gave you in a single week. I understand that the plus plan was never meant for extensive coding. But that can not be taken as an excuse that less usage is given for the same amount of money. If limits of the Plus plan as decreased, that also means that there is a decent chance that Pro 5x and Pro 20x plans had their usage nerfed.

(App in screenshot is NerfTrack)

The first image shows the API value of a weekly limit on the Plus plan before the reset, which is ~$160. Right after the reset, that value has fallen down to ~$100, which is a decrease of more than 35% of the limit. And I have felt this too, before, about 12-15 minutes of using Luna Max in fast mode drained 1% of the weekly limit. Now, with the same settings, it take ~7 minutes to drain 1%. I hope this is a temporary bug and not a permanent decrease in limits. (evidence provided in images)

Is anyone else noticing this or is it just me?

(The app used in the screenshots is NerfTrack)

Just 2 weeks ago, I posted my first prototype in this very sub-reddit, and got a really positive response from y'all with over 650 upvotes and 142K views(Previously referred to as Nerfify). I am pleased to say that starting today, NerfTrack is now available in its first public beta on GitHub (currently verified for macOS x86 and arm64). If you are seeing this post without having seen my previous one, think of NerfTrack as a stock market app, but instead of tracking stock prices, NerfTrack measures the weekly limit API equivalent cost every 10 seconds by going through local Codex logs(and yes, it also imports your existing Codex logs from months ago too). I have now achieved a 99.3%-100% accuracy with the API cost calculation compared to the unreliable graphs I showcased in my first prototype. NerfTrack tracks your limits overtime, so you reliably know wether OpenAI has either nerfed or increased limits. In my last post, a few of you claimed that such graphs are of no value since everybody knows if limits are nerfed. But NerfTrack, on the other hand, not only tells you if limits are nerfed, but also how much they have been nerfed, and when. A few 100 Codex users with reliable graphs showing proof of nerfed limits can bring a significantly larger impact than 1000s who complain with just "I feel it, but can't prove it". NerfTrack remains fully local, so worry not about your privacy.

Current known bugs and limitations(to be cared for in later versions):

-NerfTrack shows unreliable metrics if you are using fast mode, since fast mode uses 2-2.5x as much usage as standard, so you may notice a sudden drop in API prices tracking if switching from standard to fast mode

-If you use Codex on multiple devices, metrics become unreliable since that's a limitation of not NerfTrack, but the fact that logs recorded by Codex are local only and not shared between devices.

-Several buttons and interactive elements may be buggy or disabled for the current beta.

-(unconfirmed) NerfTrack may or may not work on Windows machines, especially arm64. As I currently have access only to a Mac, I could not test NerfTrack on Windows, though NerfTrack is cross-compatible on paper with releases for both macOS and Windows on GitHub.

-The current Beta has no functionality for fetching API prices from the web, so if OpenAI changes pricing of models, or releases a new model, the graph would show outdated prices. A web-fetch feature is intended to be added soon.

I would be happy to have volunteers test NerfTrack's first beta so I can continue to improve its performance and make it as bug-free as possible. Do note that it's currently a MVP so loads of features are intended for the future, but for now, it may not be as feature rich as one might want it to be.

People who do download NerfTrack, please make sure to drop a screenshot of your 3 month graphs along with what plan you are on (and ofc leave it a star to support), so we may compare each others' graphs. In the future, I will work on a website for this very purpose where users will be able to volunteer and share their graphs + plan online so others can compare against their own.

Link to NerfTrack on GitHub: NerfTrack GitHub

Link to my first prototype post on Reddit for context

>

OpenAI kept Nerfing our limits- so I built something to prove it instead of complaining without proof, so meet Nerfify! It's currently in the development stage, and I have achieved a functional prototype with reliable information, with a few UI/UX bugs here and there. Using local token consumption logs, Nerfify estimates an estimate of the API worth of one weekly limit after every 10 seconds. Think of it like a stock market app, but instead of tracking stock prices, Nerfify tracks the API value of one weekly limit over a period of time. It's still in the development stage and the first version will land on GitHub not to long from now. Do note that it won't work reliably if you use ChatGPT Work or Codex on multiple devices, since data is taken from local Codex logs only.

As the screenshot shows, it seems that our limits have been more than halved (do not mind the UI bugs, since it's just at a prototype stage, and current values may need a bit fixing since accuracy may not be up to mark)

Not many people know about this, so that's why I thought it would be good to mention. This works with both Claude Code, Codex, and many other tools like OpenClaw, OpenCode, and Hermes as well.

So the first thing you need to do is install CC Switch from Github, which allows you to change the configuration for Codex and other tools etc. After you have installed the latest release do the following steps: (in my case I am using the provider zyloo.io, and you can use any other of your choice)

• Go to Settings > Routing > Local Routing and enable all routing settings, and turn on the toggle for Codex
• Once you enable routing, head to the Claude Desktop/Claude Code tab depending on what you use.
• Click the "+" button and select "Custom Provider" (or one of the preset options if the provider you are using is available).
• Enter "Zyloo" for the provider name.
• Enter "https://api.zyloo.io/v1" for the API endpoint.
• Enable model mapping, then select OpenAI Chat Completions for the API format.
• Click "fetch models" and select the models you need from the drop down menu.
• Click Save.
• Click "Enable" for the provider setting you just made. (Make sure routing is enabled for the Claude Desktop/CLI tab)

Hope this helps!

(Plz don't mind that this report was AI generated as it was generated by Codex cuz only it could give the level of details I needed to why our limits are draining so much). Please paste the above report to your own Codex with GPT 5.6 Sol and ask it to run a deep analysis of Codex on your machine and wether or not you're experiencing a similar issue. If so, please report the issue to OpenAI so we get some attention. Since the new 5.6 lineup is so more efficient than GPT 5.5 limits should not be this bad unless there is a major problem like mine.

Paste the following prompt into Codex GPT 5.6 Sol and drop down what it said in the comments so we can know if this is OpenAI nerfing limits or there is a genuin problem wiht OpenAI's backend:

Prompt

)

I’ve been investigating unusually confusing Codex usage-limit behavior on my Plus account.

This is not simply a complaint that long tasks consume a lot. I checked the local Codex token telemetry and separated genuine token consumption—including parallel child agents—from apparent UI jumps.

The unusual part is that adjacent responses sometimes return completely different limit states, for example:

• 69% used → 4% → 69% within seconds
• 26% used → 3% → 26% within about 11 seconds
• Five-hour reset times changing before the earlier window expires
• Weekly usage dropping to zero and later returning
• The UI temporarily showing 99% remaining before jumping back to the higher-usage record

The percentage and reset information comes from server-returned rate_limits telemetry, not a percentage calculated locally by the client.

Some high-consumption tasks were legitimate. For example, one task used several parallel child agents, and their combined token usage explained most of the increase. But legitimate usage cannot explain a meter losing and restoring dozens of percentage points within seconds.

My current theory is that the account is being served multiple representations of the same intended allowance—possibly different metering shards, entitlement keys, or account records. I cannot determine locally whether this affects enforcement or only reporting.

OpenAI also documented a June 2026 Codex incident where abuse/fraud-prevention systems incorrectly rate limited certain accounts, although I cannot prove that is the cause here:

OpenAI status page

Has anyone else seen their Codex five-hour reset time move forward before the current window expired, or their remaining usage suddenly reset and then jump back?

Here is the report Codex generated:
Report