DEV Community

Cover image for OpenAI Is Merging Your ChatGPT and Codex Allowances Into One Shared Pool in December — Explained Honestly
Paul Lovelace
Paul Lovelace

Posted on Originally published at toolsdig.com

OpenAI Is Merging Your ChatGPT and Codex Allowances Into One Shared Pool in December — Explained Honestly

OpenAI is about to change how your subscription is metered, and if you split your day between chatting and coding, you will feel it. Starting in December 2026, ChatGPT and Codex will draw from one shared token-based allowance for Plus, Pro and Business subscribers. Two buckets become one pool. That sounds like a simplification — and in some ways it is — but it also means a heavy afternoon of Codex work now competes directly with the allowance you would otherwise spend in ChatGPT.

Nothing here is sponsored — no affiliate links on this page. This breaking article is not the daily buyer-intent post. Facts below come from the sources listed at the end, checked 1 November 2026. Where OpenAI has not published a detail, we say so plainly instead of filling the gap.

What is actually changing

Today, ChatGPT and Codex each have their own usage allowance. From December 2026, Plus, Pro and Business subscribers get one combined allowance across both products. Everything you do in ChatGPT's agent features and in Codex — through ChatGPT, your code editor, or the terminal — draws from the same pool.

OpenAI links the change to bringing ChatGPT Work's agent features into the main ChatGPT experience. Codex, the company's coding tool for engineering work, is being folded more fully into that ecosystem, and a single meter follows naturally from that.

Usage is measured in tokens, and how fast you burn through the pool depends on what you ask for. Advanced models and complex tasks generally use more; a quick question costs far less than a long agentic coding run. That is the same token-based logic OpenAI moved to in April 2026, when it replaced per-message estimates with credits per million tokens — a system designed to reflect the real computational cost of different tasks rather than treating every message as equal.

Who this hits

  • Plus subscribers — chat and Codex now share one allowance. If you code with Codex on weekends and chat during the week, the two now draw from the same well.
  • Pro subscribers — same shared pool, with the plan structures that already differ: Pro plans do not carry a 5-hour limit, while Plus and Business plans do, and Pro users may still face weekly caps. How those weekly caps interact with the combined allowance is one of the open questions below.
  • Business subscribers — one metered balance to track and forecast instead of two. For a team, that is arguably the cleanest win here: a single number for budgeting, rather than two allowances that run dry at different times.
  • Free users — not covered by this change. The shared pool is a paid-tier change only.

What stays outside the meter

One important carve-out: Instant chat will not draw from your usage. OpenAI states this explicitly. So your quick, lightweight chats are not competing with your coding runs — only the heavier, metered work draws from the pool. If most of your ChatGPT use is light chat, this change may barely touch you.

What happens when you hit the limit

Three options, unchanged in shape from today:

  1. Wait for the reset. Combined remaining usage and reset times will be visible under Settings → Usage, so you can see exactly where you stand instead of guessing across two products.
  2. Upgrade your plan. A higher tier buys a bigger pool.
  3. Buy credits for eligible features. For features where credit purchase is offered, you can top up rather than wait.

OpenAI expects most users will not need to wait for resets more often than they do now. Treat that as OpenAI's own expectation, not a guarantee — it is a forecast about typical usage, and heavy users are exactly the people whose experience will test it.

The practical consequence: plan your month, not just your day

Here is the shift that matters in practice. Under separate allowances, a Codex-heavy week could leave you locked out of coding while chat allowance sat unused — annoying, but contained. Under one pool, the trade-off moves inside your own account: a big Codex sprint on Monday eats the allowance your Thursday brainstorming would have used. The flip side is just as real — allowance that used to sit stranded in one product can now cover the other.

For developers, that is mostly good news: no more running dry in Codex while ChatGPT credits go untouched. For teams on Business plans, the single balance is easier to forecast. But for anyone who leans heavily on both products in the same month, the new discipline is simple — check Settings → Usage before starting a big run, and remember that the expensive model on a complex task burns the pool fastest.

What OpenAI has NOT published — and why it matters

  • No exact December date. OpenAI has said December, not a day. Do not trust any post that claims a specific launch day yet.
  • No per-plan allowance amounts. Nobody outside OpenAI knows yet how big each plan's shared pool will be, so nobody can honestly tell you whether your plan gets effectively bigger or smaller.
  • How weekly Pro caps interact with the combined pool is still unclear, as is whether Plus and Business users will find their 5-hour limits more restrictive once Codex draws from the same balance.

That last point deserves emphasis, because OpenAI's allowance numbers have moved before. In October 2026 it doubled Pro 100 and Pro 500 allowances and cancelled a planned reduction for Pro 200 — after notifying subscribers of the shared-pool change at checkout without giving a start date or plan allowances. Anyone building workflows around current limits should expect the numbers to move again.

How this fits the last few weeks

This is the second OpenAI usage change in days, and it is easy to confuse with the first. On 30 October, OpenAI reversed a planned ChatGPT Pro cut and doubled Work and Codex limits — that was the old story, already covered here. The shared pool is the new one: it does not change how much you get (amounts are unpublished), it changes how what you get is counted. Separately, Pro and Business subscribers are also in line for monthly API credits — a different benefit, not part of this pool. Keep the three stories apart, and you will read December's announcement correctly when it lands.

The bottom line: one pool is simpler to understand and fairer in one specific way — your allowance follows you between chat and code instead of being trapped in one product. But simplicity is not the same as generosity. Until OpenAI publishes the date and the amounts, the honest position is: watch Settings → Usage in December, keep your heavy runs deliberate, and do not let anyone sell you a number that does not exist yet.


Sources: OpenAI Help Center, "Understanding ChatGPT and Codex usage limits" (updated 31 October 2026), via the reporting below; TokenPost, "OpenAI Will Combine ChatGPT and Codex Usage Allowances in December", 31 October 2026, https://www.tokenpost.com/news/technology/45608 ; CryptoBriefing, "OpenAI to merge ChatGPT and Codex token allowances in December 2026", 31 October 2026, https://cryptobriefing.com/openai-unifies-chatgpt-codex-token-allowance/ ; PANews, 1 November 2026; Automater.ai, analysis of the OpenAI Help Center page.

Top comments (0)