OpenAI is merging two quotas that are separate today. The official ChatGPT and Codex usage limits page was updated in early November and states that, starting in December, Plus, Pro and Business plans will have a single usage quota, shared between ChatGPT and Codex, measured in tokens. Instant chat stays out of the count.
The change is small in the sentence and big in the day to day of anyone who writes code. Until now, spending the coding quota did not affect what was left for chatting. Starting in December, it does.
What actually changes in December?
Two things: the pool is no longer separate, and the unit of measurement becomes tokens. The rest stays roughly the same. You can see the combined balance and the reset time in Settings → Usage, and anyone who hits the limit can wait for the reset, change plans or buy credits for eligible features.
| Attribute | Until now | Starting in December |
|---|---|---|
| Where the quota applies | ChatGPT and Codex with separate limits | One quota, split between both |
| How it is measured | A limit per product and per model | Tokens, depending on the model and task complexity |
| Where to see the balance | Per product | Combined balance and reset in Settings → Usage |
| When it runs out | Wait for the reset or change plans | Wait for the reset, change plans or buy credits |
Source: OpenAI's official ChatGPT and Codex usage limits page, updated in early November 2026 and checked on 2026-11-06.
Why are subscribers not convinced?
Because the merger lands on top of a distrust that already exists. Over the last two weeks, subscriber forums have turned into a queue of reports about quota that disappears faster than the user's own math predicts.
- On 2026-11-04, a r/codex thread with 66 comments summed up the fear of people using the Plus plan to ship a project: if chat also consumes the quota, coding work shrinks.
- On 2026-11-05, another r/codex thread with 64 comments shows the problem that predates the merger: the author opened the topic believing the limit had doubled, then edited the post to correct himself, saying nothing had doubled. If subscribers cannot read the current limit, the December change arrives at the worst possible moment.
- On 2026-11-06, a r/ChatGPT thread with 54 comments shared a screenshot of the official page itself and the account of a Plus subscriber who expects his workflow to break.
The other side is legitimate and it is on the page itself: the change exists to bring Work's agentic capabilities into ChatGPT, and OpenAI says it expects most users will not need to wait for their usage to reset more often than they do now. A shared quota also has a real upside: people who do not use chat can spend everything on code, and people who do not use code can spend everything on chat.
The problem is not the idea of sharing. It is the meter that will govern the pool.
What do the 81 abnormal usage reports show?
Since 2026-08-27, the Codex repository has kept a tracking issue open, #41220, with 81 comments and the bug and rate-limits labels. It does not claim a single root cause. It gathers reports that, together, show an uncomfortable pattern: usage does not match what the client itself records.
Three examples cited in the tracker:
- #38728: same account, same 7-day bucket, same reset timestamp and same service tier. The meter accelerated about 2.4x mid-window and then returned to the previous range.
- #40067: the agent's local logs added up to about 9.39 million input tokens. The official profile attributed 81.7 million to the same account.
- #37445: a controlled experiment with 103h47m of clients closed and 0% usage. Opening the desktop app triggered a fixed deduction of about 6% of the weekly quota, and quitting the app stopped the drain.
None of this is confirmed by OpenAI, and the tracker is explicit about that. But the practical conclusion does not depend on who is right: if the number that decides your day cannot be audited on your side, you are spending on trust, not on a budget. In December, that same trust will also apply to chat.
Can you audit your own Codex usage?
Partly. Codex exposes three useful layers, and none of them is an official audit tool.
- Status line. The
/statuslinecommand configures what appears in the footer, and the item list includes primary and secondary usage limits./statusshows the active model, approvals and the session's token usage. - Local logs. Each session writes a
rollout-*.jsonlfile under~/.codex/sessions/. It is the closest source to what the client saw. - Third-party audit. Tools such as usage-engineer read those logs and group usage by day. Install it with
pipx install git+https://github.com/noamshorts22-prog/usage-engineerand runue audit --by-day --days 14.
The limit of that audit is the same as the problem: anything applied on the server, such as per-model weighting, background activity or credit reconciliation, does not appear in the local log. That is why two reports can diverge without the user getting the math wrong.
What does this teach anyone paying for a quota?
Three things, and none of them is specific to OpenAI.
- A shared quota turns two decisions into one. Every chat question now competes with the next coding task. Anyone who codes and chats on the same plan loses a separation that used to be free.
- Tokens make the cost of a task less predictable for the user. Reprocessed context, repeated attempts, subagents and polling all enter the bill. The tracker cites a case where 19.8% of the local token volume came from turns whose only action was to wait or check status.
- Measurement you cannot audit is not a budget. It is trust. When the pool is single, a measurement error stops being a billing detail and becomes a product decision.
Where does Verboo Code stand in this story?
Verboo Code does not sell messages and does not charge per token inside the plan. Pricing is fixed per plan. On the Junior, Pro, Max and Ultra plans, the delivery is unlimited tokens, and what varies between models is speed, not the price of the quota. The /usage command shows your group's rate-limit windows, how much has been used and when each one resets.
That does not make the choice free. If a task requires one specific frontier model, Verboo Code may not be the right tool for it. What it does solve is the December question: when chat and code share the same ceiling, every study question starts to have an opportunity cost inside the plan.
If your December problem is deciding between spending the quota on chat or on code, Verboo Code separates the two: fixed price per plan and a rate-limit window you can see in /usage. You can start at verboo.ai with your own repository.
