Invest1 distinct publisher3 min readUpdated
Codex lead Thibault Sottiaux says weekly caps were not cut. Paying developers on $200-a-month plans are cancelling anyway, because OpenAI publishes no map of what consumes an allowance.
The Investor · Invest desk

Compiled by The InvestorSomething wrong?How this is made
OpenAI's head of core products, Thibault Sottiaux, who now runs both ChatGPT and Codex, said on August 21 that the company does not adjust usage caps without talking to the community, and pointed instead at third-party "sub2api" tools that repackage a ChatGPT subscription so it can be called like OpenAI's metered pay-as-you-go API [1][2][3]. The explanation is doing little work with customers, because OpenAI shows a rounded percentage bar and no clear map of what actually consumes a weekly allowance, so no paying team can audit the claim from the outside [4][5].
The complaints are specific. On OpenAI's developer forum, a Codex 20x subscriber posting as anil.c1 wrote on August 14 that he was burning a full weekly allowance in roughly five hours while doing the same work as before with plain Codex Desktop and no extra tools; four days later he posted again to say he had cancelled [6][7]. Another user, "plutavian," reported that a brand new 20x account carried a weekly limit of about $200 in API-dollar terms while an older account on the same plan still showed over $2,000 [8], a gap of at least tenfold on identical paid tiers [1]. A developer named Ayaan Lashari published a free tool, NerfTrack, on GitHub that reads Codex usage data and translates the percentage bar into dollars [9].
An investigation by Kingy AI rated the claim that limits were secretly cut as "supported but unproven," noting that a smaller allowance and faster consumption of an unchanged allowance look identical on a rounded percentage bar [10][11]. That is the whole problem in one sentence. Kingy AI also flagged an August 20 post by Alex Getman claiming a Plus allowance had fallen from about $160 to about $80 in API-dollar terms [12], a halving if accurate [2].
The sub2api story also sits awkwardly against OpenAI's own documentation, which, per the Cryptopolitan account, states that subscription access and API-key access are billed on separate tracks [13]. And this is the second flare-up in two months [14]. On June 30 Sottiaux held a Sunday "warroom" and explained the first round as Codex doing unintended extra work, with automated review tools and helper subagents sometimes running twice or over-trying error fixes [15][16]. He said the dashboard had displayed activity that was never charged, that fixes shipped, and that limits were fully reset [17]. On July 28, according to Kingy AI, he addressed another round by saying GPT-5.6 Sol makes more tool calls and runs longer, and that OpenAI had tuned it so normal use lasts about 18% longer, while again denying any cut to subscription limits [18].
Underneath all three episodes is an accounting surface nobody can reason about. OpenAI's help center says Codex, ChatGPT Work and related tools draw on one shared allowance, and that consumption depends on model, where the task runs, complexity, context, reasoning effort, speed and tools used [19][20]. Kingy AI notes Fast Mode runs GPT-5.6 about 1.5 times faster but spends credits at 2.5 times the normal rate [21], meaning roughly 1.67 times the credits for the same work, paid for in wall-clock time [3]. A team cannot forecast a $2,400-a-year seat against that [4].
The operator lesson is not about model quality. It is that a spend cap you cannot read is an unpriced input, and unpriced inputs get removed from build plans. Watch whether OpenAI ships a per-task usage ledger in dollars rather than a percentage bar, whether it publishes multipliers per model and mode, and whether it names sub2api enforcement as policy instead of as an explanation after the fact.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
Four days after his August 14 post, anil.c1 posted again to say he had cancelled his plan.
Some users are cancelling $200-a-month plans, and developers have flooded forums and X claiming their paid Codex allowance drains far faster than before.
Thibault Sottiaux is OpenAI's head of core products and now runs both ChatGPT and Codex.
OpenAI still publishes no clear map of what consumes a Codex allowance.
A developer named Ayaan Lashari built a free app called NerfTrack that reads Codex usage data and shows the weekly value in dollar terms, and put it on GitHub.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Single-publisher relay of unverified user reports
Everything rests on one article from one publisher, which itself relays forum posts, an X statement and a third-party investigation. Statements of record (the denial, the sub2api attribution, the help-center consumption factors, the June 30 warroom account) are firmly attributed, but every quantitative claim about shrinking allowances is secondhand and unaudited, and the cited investigation explicitly rates the core claim unproven with conflicting trackers.
Real paid usage and tooling response, unquantified scale
There is concrete evidence of real deployment and reaction: paying subscribers on $200-a-month 20x plans running Codex Desktop daily, at least one documented cancellation, forum and X activity, a shipped third-party usage tracker on GitHub, and a prior operational remediation with a full cap reset. What is missing is any count of affected accounts, download or star figures for NerfTrack, or churn numbers, so scale cannot be established.
Cut narrative outruns the available proof
The framing that paid Codex limits are shrinking is carried by anecdotes and derived API-dollar estimates that the one investigation cited declines to confirm, so the strongest reading of the story is overstated relative to evidence. The gap is moderate rather than large because the documented, verifiable core — no consumption map, percentage-only meter, shared allowances, an admitted prior over-consumption incident — genuinely supports the transparency complaint even if the 'secret halving' does not.
Interested parties on every side of the meter
Each actor in the chain has a stake: OpenAI's product lead is defending both a pricing structure and the company's transparency record while attributing burn to resale tooling its own docs say is billed separately; cancelling subscribers are making a public case about money they paid; NerfTrack's author gains standing from a distrusted vendor meter; and the publisher is a crypto-and-frontier-tech outlet that appends a newsletter solicitation mid-article. No party publishes the underlying usage data that would settle it.
Low — one outlet, contested core fact
Confidence is limited by a single-source cluster whose central factual question is explicitly unresolved by the investigation it cites. Attributed statements, the documented transparency gap and the June 30 remediation are reliable enough to act on; the magnitude claims about allowance cuts are not, and no cross-publisher corroboration exists to raise the floor.
leadership
Agents That Click: OpenAI Ships Computer Use, And Credential Policy Becomes Your Problem1 distinct publisher
build
Codex learns to click: the coding agent stops typing patches and starts operating the machine1 distinct publisher
build
Developer habit, priced at $965B: what Anthropic's run actually proves1 distinct publisher
build
OpenAI's $8 reset button turns a flat ChatGPT seat into an unbudgeted line item1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 21, 2026