Codex users are not just grumbling about a quota bar. They are pointing to the same problem again and again: OpenAI sells higher limits, but still gives developers too little visibility into what they are actually buying.
The complaint now moving through Codex circles is simple enough. Some users say their weekly allowance is draining much faster than it did before, and a small tracking project called NerfTrack has become part of the evidence. Its GitHub repository, published by Ayaan Lashari, describes a local Tauri desktop app that reads Codex usage records and estimates their API-equivalent weekly value. That part is real.
The harder claim is the one users care about most: whether OpenAI quietly cut the usable allowance. There is no public quota table that lets you prove that cleanly. OpenAI's own help material says usage limits vary by plan, workspace settings, system conditions and individual usage, and that ChatGPT displays applicable limits and reset times where available. If you're paying for Codex to do serious engineering work, that is not enough.
People notice the gap.
Codex Users Are Measuring What OpenAI Won't Publish #
NerfTrack exists because the official meter doesn't answer the question developers are asking. A quota bar can tell you that usage is gone. It doesn't tell you whether one repository-wide refactor, one long planning session or one model choice consumed the allowance. A tool that converts local records into estimated API-equivalent value is an imperfect workaround, but it is also a rational one. Developers measure systems for a living. When the product gives them a black box, they build a gauge.
AI Agents Autonomously Hacked Taiwan's Government for Four Days Straight Researchers at the Israeli-Austrian firm Dream say suspected China-linked hackers used open-source AI agents to autonomously breach Taiwan's government over four days in July, compromising 85 accounts and stealing 2,500 records with almost no human oversight. The campaign, built on the Hermes and OpenClaw frameworks, later expanded to Taiwan's... - ai agents autonomous hacking government systems - taiwan government data breach four days
OpenAI's developer forum shows this was not a one-day Reddit mood swing. In an April 10 thread titled "Understanding the New Codex Limit System After the April 9 Update," a community member argued that users needed to stop thinking in message counts and start thinking in reasoning time. The post estimated that, on one Plus setup, roughly 40 minutes of reasoning could consume a full five-hour limit window. It was not an official formula, but the discussion captured the practical experience: the same prompt count no longer meant the same work.
That distinction sounds technical until you're the person blocked by it. A founder, engineer or freelancer does not buy a $200 monthly plan because they enjoy watching quota mechanics. They buy it because Codex is supposed to keep a project moving. If the allowance can vanish after a few heavy runs, the plan becomes harder to budget than a cloud bill with no line items.
Frankly, this is where OpenAI's silence hurts it. The company does not have to publish every internal cost model or abuse-control rule. It does need to tell paying users enough to plan a working day. A vague dynamic limit may be defensible at OpenAI's scale, but it is a poor interface for people using Codex as part of production work.
The Complaints Are Specific Enough To Take Seriously #
On July 20, a Pro 20x user posting as D_Anil_Reddy wrote on OpenAI's developer forum that they had moved from ChatGPT Plus to Pro 5x and then Pro 20x, only to exhaust both the weekly Codex allowance and the GPT-5.3-Codex-Spark allowance sooner than expected. The same user said roughly 2,000 rupees of additional Codex credits were consumed within only a couple of substantial engineering prompts. That is not a generic dislike of limits. It is a user trying to understand why a paid workflow became unpredictable.
OpenAI Support replied on July 23 that a full per-task usage breakdown did not appear to be available, pointing instead to the Codex Usage Dashboard and the /status command during an active Codex CLI session. The support answer also said the request for task-level breakdowns would be logged. That is useful as far as it goes. It does not go very far.
Another public signal came from GitHub. In an Aug. 1 issue on the openai/codex repository, a ChatGPT Pro 20x user reported that a weekly Codex allowance reset to 100% and then fell to 91% during one GPT-5.6 Sol engineering session. The same issue said the previous weekly allowance had been nearly exhausted in about one to one and a half days, and that the user had bought $40 in extra usage to continue. Again, this does not prove a secret quota cut. It does prove users are seeing enough volatility to file detailed reports with dates, versions, models and operating systems.
OpenAI's own GPT-5.6 documentation adds another wrinkle. Its help center says GPT-5.6 Sol and Sol Pro are rolling out across eligible paid plans, while Codex access depends on plan and product. It also says limits continue to depend on plan settings and availability. So when a user switches models, sees usage drain faster and gets no clear cost explanation, the confusion is not irrational. The documentation leaves room for it.
A Federal Judge Ruled Judges Are Immune Even If AI Wrote Their Rulings A federal judge ruled that judicial immunity protects a Nevada family court judge even if she let AI write her entire ruling, botched wording included. The August 17, 2026 decision in Phillips v. Parlade means judges can't be sued over AI use in their orders, though appeals and judicial conduct complaints remain open. - judicial immunity covers AI generated court rulings - can judges use artificial intelligence to write rulings
OpenAI should fix the meter before it argues about the complaints. Show task-level usage. Show what model, context size, tool calls and reasoning effort did to the allowance. Show enough history for a developer to compare yesterday's run with today's. Cloud platforms learned this years ago: people tolerate cost when they can see the bill forming. They get angry when the bill feels like weather.
Also read: AI Agents Autonomously Hacked Taiwan's Government for Four Days Straight • Moonshot AI's Kimi K3 Undercuts GPT and Claude While Proving Its Numbers • A Federal Judge Ruled Judges Are Immune Even If AI Wrote Their Rulings