The short version
From December, coding with Codex and working in ChatGPT will spend the same budget. OpenAI updated its help center on October 31, 2026 to say Plus, Pro and Business plans will get one token-based allowance shared across ChatGPT and Codex. For teams building on OpenAI tools, the practical question is no longer “how many seats” but “how many tokens each person burns, and on what.”
What exactly is OpenAI changing?
OpenAI’s help article on ChatGPT and Codex usage limits says that, starting in December, the allowance on Plus, Pro and Business plans will be shared across ChatGPT and Codex. The company ties the change to bringing the agentic capabilities of its Work mode into the main ChatGPT experience. Usage will be counted in tokens, so the amount used depends on the model a person picks and the task they ask it to do.
Two details matter for everyday work. Instant chat will not draw from the shared allowance, and the combined remaining usage and reset times will be visible in Settings under Usage. When people hit the cap, OpenAI says they can wait for a reset, move to a higher plan or buy credits to keep using eligible features. OpenAI has not published per-plan token figures or an exact December switch-over date.
Why is this happening now?
The limit change arrives with a product reshuffle. TechCrunch reported on November 2 that OpenAI is merging the Chat and Work tabs in its ChatGPT desktop app, starting with a small group of users, while Codex stays a separate experience inside the same app. 9to5Mac reported that the older ChatGPT Classic app will be retired on January 30, 2027. TechCrunch also notes that Anthropic merged Claude’s chat and Cowork modes into one interface in September, so a single workspace with a single meter is becoming the norm for AI assistants.
OpenAI says it is preparing the switch carefully and expects most users will not have to wait for usage to reset more often than they do now. The New Stack framed the change as one that “pits ChatGPT against Codex,” reflecting concern among developers who use chat for research and planning and Codex for the coding itself.
What it means for US & EU software teams
For most teams, the risk is not cost but interruption. A developer who reaches the shared cap in the middle of a refactor loses both the coding agent and the assistant they would use to think through the problem. Agent-heavy work, such as long autonomous Codex runs, large reviews or test generation across a repository, is exactly the kind that consumes the most tokens. That makes it worth separating predictable interactive work from bursty automated work.
Procurement and governance follow from that split. Developers on personal Plus or Pro plans sit outside company controls, while a Business workspace gives admins visibility. Work billed through API access is metered separately from ChatGPT plans and can carry its own budget and alerts. For EU clients and regulated FinTech or HealthTech projects, keeping coding agents on company-managed accounts also makes it easier to show who generated which change and under which data terms.
What should teams do before December?
- Inventory accounts. List who uses Codex and on which plan, and move work done on personal subscriptions into a managed Business workspace where possible.
- Separate interactive and automated work. Keep long-running or scheduled coding jobs on metered API access with a dedicated budget, so they do not drain individual allowances.
- Set model defaults. Agree which tasks justify the heaviest models and use lighter ones for routine edits, since model choice drives token use.
- Watch the Usage page. Track combined usage and reset times in the first weeks of December and adjust plans before people get blocked mid-sprint.
- Avoid single-tool dependency. Keep prompts, agent instructions and tests in the repository so work can continue in another tool if limits bite.
Frequently asked questions
What is changing with ChatGPT and Codex usage limits?
OpenAI’s help center, updated on October 31, 2026, says that starting in December the usage allowance on ChatGPT Plus, Pro and Business plans will be shared across ChatGPT and Codex. Usage is measured in tokens, so the model you choose and the complexity of the task decide how quickly the allowance is used.
Does every ChatGPT message count against the shared allowance?
No. OpenAI says Instant chat will not draw from the shared usage allowance. Agentic work, more advanced models and complex tasks generally use more of it. Combined remaining usage and reset times will appear in Settings, Usage.
What happens when a team member hits the limit?
According to OpenAI, users can wait for the allowance to reset, upgrade to a higher plan, or buy credits to keep using eligible features. OpenAI says it expects most users will not need to wait for resets more often than they do today.
How should engineering teams prepare?
Check which developers use Codex on personal Plus or Pro plans versus a Business workspace, decide which tasks justify heavier models, keep long-running or automated coding jobs on metered API access with its own budget, and watch the Usage page during the first weeks of December.
Sources
OpenAI Help Center — Understanding ChatGPT and Codex usage limits (primary source, updated October 31, 2026)
TechCrunch — OpenAI is finally merging ChatGPT’s Chat and Work tabs (November 2, 2026)
9to5Mac — OpenAI is retiring ChatGPT Classic app, will soon combine Chat and Work tabs in new app (November 2, 2026)
The New Stack — OpenAI’s new shared usage limit pits ChatGPT against Codex (November 2, 2026)