Starting in December 2026, your ChatGPT chats and your Codex coding work will draw from one shared usage allowance, measured in tokens. That’s the short version of a change OpenAI published in its Help Center article “Understanding ChatGPT and Codex usage limits”, updated October 31, 2026. If you pay for ChatGPT Plus, Pro, or Business, this affects you. Instant chat — the fast default model — will not draw from the allowance, and OpenAI says it expects most users “won’t need to wait for their usage to reset more often than they do now.”
That last sentence is doing a lot of work, and it’s worth reading as a forecast rather than a promise. OpenAI has not published the size of each plan’s new allowance, and it has not pinned down an exact start date inside December. So the honest version of this story is: a real, confirmed change with two big numbers still missing. What you can do about it, though, is concrete — and November is the month to do it, while your current split limits still give you a clean baseline to measure against.
What actually changes in December
Right now, most paid subscribers effectively live with two budgets. Chat with the advanced models has its own limits, and Codex (plus ChatGPT Work, ChatGPT for Excel, and Workspace Agents) already shares a separate agentic allowance. From December, OpenAI says your plan’s “usage allowance will be shared across ChatGPT and Codex,” and that usage “will be measured in tokens, the units of information a model processes and generates.”
In plain English: the long coding session that used to eat only your Codex budget and the long research chat that used to eat only your chat budget will now eat the same budget. The model you pick and the task you ask for decide how fast it drains — OpenAI’s own wording is that “more advanced models and complex tasks generally use more of your allowance.” Your combined remaining usage and reset times will show in Settings, under Usage, and there’s a web dashboard at chatgpt.com/codex/settings/usage.
Here’s the change in table form:
| Activity | Today | From December |
|---|---|---|
| Codex coding work | Shares the agentic allowance with Work | One shared allowance across ChatGPT and Codex |
| Chat with advanced models | Separate chat limits | Same shared allowance |
| Instant chat (fast default model) | Outside the metered pool | Still exempt — “will not draw from your usage” |
| Image generation, file uploads, regular voice | Separate limits today | OpenAI has not said how these fit into the new allowance |
That last row matters. Don’t assume your image generations are suddenly free, and don’t assume they’re suddenly metered either. OpenAI hasn’t said. Treat anything it hasn’t documented as unknown, not as good news.
Who gets hurt most — and who probably won’t notice
I spent a while thinking about who actually feels this, because OpenAI’s “most users” line smooths over a real split in its customer base.
You’ll probably barely notice if: you use ChatGPT for everyday questions and rarely touch Codex, or you use Codex heavily but almost never chat with the advanced models. One dominant use plus a little of the other fits inside a single pool about as well as it fit inside two.
You’ll feel it first if: you’re the person who does both at full tilt. The freelance developer who debugs in Codex all afternoon and then leans on ChatGPT’s advanced models for client proposals in the evening. The small team where one Business seat runs an agentic workflow and the same seat handles research chats. The founder who prototypes with Codex and writes the pitch deck copy in ChatGPT. For these users, two budgets becoming one isn’t a paperwork change — it’s a smaller effective budget for the same work, unless OpenAI sizes the new pool generously. And since the sizes aren’t published, nobody can promise you otherwise.
There’s a second group worth naming: people who bought a plan specifically because of one side’s limits. If you upgraded to Pro mainly for Codex headroom and your chats were an afterthought, your chats are now a tax on your coding budget. The reverse is true too. The December change rewards people who plan their usage as one budget, and it punishes people who keep treating the two products as separate.
The reaction in the community backs this up. Threads on r/codex and r/OpenAI drew hundreds of votes within hours of the news spreading, and according to reporting on the reaction, nearly every top comment asked the same question: how will the counting actually work? Some users openly floated cancelling Plus. That’s not proof the change is bad — it’s proof that the missing numbers are the story. People can’t plan around a pool whose size is secret.
The context: a year of moving limits
This change doesn’t land in a vacuum. OpenAI has adjusted these allowances repeatedly in 2026, and the pattern explains why subscribers are jumpy:
- In late September 2026, OpenAI added a $500 Pro tier and lowered the included allowance for new $200 subscribers, while existing $200 subscribers kept the older, larger allowance through October 29.
- On October 29–30, 2026, OpenAI doubled usage limits for Pro 100, Pro 200, and Pro 500 and for Business Premium seats, and cancelled a planned Pro 200 cut — so Pro 200’s Work and Codex usage stayed at its higher level.
- Plus, notably, got no increase in that round. Its allowance stayed where it was.
Current plan prices, as read from OpenAI’s own pages in October 2026: Plus $20 a month, Pro at $100, $200, or $500 a month (monthly billing only, no annual discount), and Business at $20 per user a month billed annually or $25 billed monthly, with a two-seat minimum. Third-party trackers describe the relative allowances as Plus 1x, Pro 100 5x, Pro 200 10x, and Pro 500 25x — those multiples come from an OpenAI employee’s public post, not from an official pricing page, so treat them as the best available shorthand, not gospel.
Why does the history matter? Because it tells you the December pool size isn’t set in stone even after it’s announced. OpenAI has shown it will double allowances, cut them, cancel cuts, and add tiers within weeks. Your job isn’t to predict the final number. It’s to build a usage habit that survives any of those numbers.
The November audit: measure your burn before December
Here’s the original, practical part of this article — the thing I’d actually do, and what I’d tell a friend paying $20 or $200 a month to do this week. You can’t plan around a secret pool size, but you can measure your own burn rate, and that measurement is the only input that matters once the pool is announced.
Step 1: Screenshot your two dashboards now
Open Settings → Usage in ChatGPT and the Codex usage dashboard, and screenshot both at the same time each week. Right now they show two separate budgets. That split view disappears in December, so November is your last chance to learn how much each side of your work actually costs. Note the reset times too — Codex already runs on a 5-hour window and a weekly window, and Pro plans have no 5-hour limit while Plus and Business do.
Step 2: Run a normal week and log three numbers
For one ordinary work week, jot down: (a) roughly how many hours you spent in Codex or Work, (b) how many long chats you had with advanced models, and (c) which side hit a limit first, if either did. You don’t need token-level precision — OpenAI doesn’t give you that anyway. You need to know which side of your work is the hog. Most people are surprised. The developer who swears Codex is the problem often discovers that three long research chats with the biggest model ate just as much.
Step 3: Sort your work into three buckets
Once you know your hog, sort your recurring tasks into:
- Must stay on advanced models — work where the bigger model’s quality genuinely changes the output: hard debugging, long-document analysis, anything you’d redo if a weaker model fumbled it.
- Can drop to Instant chat — quick questions, brainstorming, drafting, summarizing. Instant chat is exempt from the December pool, which makes it the single biggest pressure valve OpenAI handed you. Use it deliberately for the lightweight half of your day.
- Can move off-peak or batch — long Codex runs that don’t need to happen at 2 p.m. on a Tuesday. If the pool has a 5-hour window (Plus and Business do), spreading heavy runs across windows is free capacity.
This three-bucket sort is the whole strategy. Everything else — upgrading, buying credits, cancelling — is a decision you make after the sort tells you whether you have a real shortfall or just an unexamined habit.
When you hit the limit: the three documented ways out
OpenAI documents three options when you reach the shared allowance: wait for the reset, upgrade your plan, or buy credits to keep using eligible features. Each has a catch worth knowing before December.
Waiting is free and, for most people, fine — but only if your work isn’t time-sensitive. A freelancer on a client deadline can’t wait out a weekly window. Know your reset times before you need them.
Upgrading is the blunt instrument, and the math changed in October. Since Pro 100 is $100, Pro 200 is $200, and Pro 500 is $500 against Plus at $20, each step up costs real money — and since the December pool sizes are unpublished, you’re buying a bigger unknown, not a known quantity. Upgrade only if your November audit shows you hitting limits on your current plan already. If you’re not hitting limits now, December alone isn’t a reason to upgrade; it’s a reason to measure.
Buying credits is the escape valve OpenAI itself points to: Plus and Pro users who reach a limit can buy additional credits and keep working without changing plans, for eligible features in Codex, ChatGPT Work, and the Office extensions. The open question — and it’s a real one — is whether the subscription credits benefit applies to Codex overflow at all, and what credits will cost in December. OpenAI’s help pages don’t settle that yet. My rule of thumb: if your monthly credit purchases would exceed the price jump to the next tier (for example, more than $80 a month on top of Plus to reach Pro 100’s price), the tier upgrade is the cheaper pipe. Below that, credits win because you only pay for the months you actually overflow.
There’s also a fourth move people will try that I would not recommend: stacking accounts. OpenAI separately published card and device limits in November 2026 — if too many subscriptions are tied to one payment card or device, ChatGPT may block a new purchase, and signing out doesn’t guarantee a freed slot. Multi-account juggling to dodge the shared pool is exactly the kind of workaround that now runs into its own wall. Keep one primary account, know which one it is before you cancel anything, and don’t cancel a grandfathered allowance hoping to rebuy it later — pre-existing subscriptions keep working under an exception, but cancelling one doesn’t guarantee you can replace it.
A decision framework for December
When OpenAI finally publishes the pool sizes, run this check in order:
- Is the new pool at least as big as your heavier current budget? If yes, and your November audit showed you only ever stressed one side, you’re fine. Change nothing.
- Is it smaller than your combined November burn? Then shift bucket 2 (lightweight work) to Instant chat first. That’s free and immediate.
- Still short after the Instant shift? Price one month of credits against the next tier up, using the $80 rule above. Buy the cheaper one.
- Still short and time-sensitive? Upgrade — but re-audit after a month, because OpenAI’s history says the allowances will move again, and you don’t want to pay Pro 500 prices for a Plus-sized habit.
One more honest caveat: everything in this article about December rests on a Help Center article updated October 31, 2026, and on checkout wording spotted by users. OpenAI has not published a blog post announcing this change. If the wording moves — if the start slips, or the pool sizes arrive with surprises — the framework above still works, because it’s built on your measured usage, not on OpenAI’s announcement. Measure in November, decide in December, and don’t let a shared meter quietly become a paywall for work you used to do for free inside your plan.
Frequently Asked Questions
When does the ChatGPT and Codex shared usage limit start?
OpenAI says “starting in December” 2026, for Plus, Pro, and Business plans. It has not published an exact day. Nothing has changed yet — your current separate limits still apply through November.
Does Instant chat count toward the shared allowance?
No. OpenAI states that “Instant chat will not draw from your usage.” That’s the fast default model, and it’s the main pressure valve for lightweight work once the pool merges.
Will Free, Go, or Enterprise users be affected?
The December change as documented covers Plus, Pro, and Business plans. Free, Business Enterprise, and Edu plans aren’t named in the shared-pool announcement, and OpenAI’s separate card/device limits also exclude Free, Business, Enterprise, and Edu accounts from counting.
What happens when I hit the shared limit?
According to OpenAI’s help pages, you wait for the reset, upgrade your plan, or buy credits for eligible features. Combined remaining usage and reset times will appear in Settings, under Usage.
Should I upgrade to Pro before December?
Only if your November usage audit shows you’re already hitting limits on your current plan. Since the December pool sizes are unpublished, upgrading now means paying more for an unknown quantity — measure first, then decide when the numbers are public.
How do I check my usage right now?
In ChatGPT, go to Settings → Usage. For Codex, the web dashboard is at chatgpt.com/codex/settings/usage. Screenshot both weekly through November so you have a baseline before the single-pool view replaces them.
Sources and further reading: OpenAI’s Help Center article “Understanding ChatGPT and Codex usage limits” (updated October 31, 2026) as reported by 7minai and Automater. For the October allowance changes, see our earlier coverage: OpenAI Doubles Pro Limits and ChatGPT Pro 200 Usage Halved.