OpenAI doubles Pro limits and tests Work tools inside Chat

OpenAI has raised the ceiling on paid ChatGPT work and, in the same subscriber note, started merging the place where that work happens. BleepingComputer reviewed the email. Three changes are in it. Only one is already live. The other two change what an ordinary chat window is allowed to spend, and what it is allowed to touch.

On October 29, 2026, Work and Codex allowances doubled for the Pro 100, Pro 200, and Pro 500 subscriptions. Alongside that, OpenAI is preparing a single allowance shared by ChatGPT and Codex. Use of either product draws from the same pool. The note says Unlimited Instant stays in the subscription and does not count against that pool. More capable models and heavier tasks draw more of it. The remaining balance and the reset time show up under Settings, then Usage. When the pool is empty, the email’s options are to wait for the reset, move to a higher subscription, or buy credits for features that accept them.

The third change is a test of the product surface. Over the coming weeks a small group will see Chat and Work as one experience. A person in that group can start in an ordinary conversation and hand the same thread a larger job without switching modes. OpenAI says people in the test can attach files, use plugins, and ask the assistant to produce a page or a deck, or to finish tasks on the web, with the person still guiding the work. Codex stays a separate experience in the ChatGPT desktop app. The coupling is the allowance. The experiment is the window.

A higher cap and a wider pair of hands

A doubled allowance is capacity for people who were hitting the old ceiling. A shared allowance is contention for any team that runs Codex hard and also expects Chat to answer the same day. A long coding session can empty the pool a support workflow still needs. The usage panel is the practical check, and it is worth reading before someone buys credits to paper over a workflow that should have been split.

The security change is the test, not the quota. Files, plugins, and actions on the web are permissions. A chat that only replies and a chat that can open an attachment, call a plugin, and act on a site are different systems wearing the same name. The second system inherits the prompt, the paste, and every plugin the account is allowed to call. OpenAI says the person stays in the loop to review and guide the work. Review is a control only if someone is actually watching, and only if the plugin list was chosen on purpose.

What to do before the test widens

Find out whether anyone on staff is in the combined Chat and Work group. Treat those accounts as assistants with tools. Remove plugins that can reach mail, files, or production systems the test does not require. Keep tokens, secrets, and customer data out of a thread that can carry a task onto the web. An attachment in that thread is an export.

If Codex and Chat now bill one pool, decide which workflow is allowed to spend it. Watch the reset time before a burst of agent work collides with a person who still needs the chat side for the job in front of them. Official clients still come from OpenAI. A mode that can finish a task on the web is still the company’s assistant, acting with the reach of the signed-in user. The vendor’s test does not move that reach. It makes the reach easier to use from the same box where people type half-finished thoughts.

This briefing relies on public reporting by BleepingComputer, including the subscriber email OpenAI sent.