OpenAI is merging ChatGPT's separate Chat and Work tabs, TechCrunch reported on November 2, 2026. The reporting does not set out a timeline, a migration path or what happens to existing projects, and this briefing does not supply them.
Why the split existed
The consumer/enterprise split was never a technical boundary. It was an interface convention borrowed from the rest of software, where a personal product and a work product are sold to different buyers with different expectations: separate data handling, separate billing, separate promises about who owns what.
Separating a work surface from a personal one is how a company sells the same model twice. It also lets an administrator make claims about data isolation that are difficult to make about a single shared surface. That is why the split appeared, and it is the reason its removal is not a cosmetic decision.
The one-assistant thesis
The read: merging the surfaces is the interface expression of a thesis the whole industry has been drifting towards — that a person has one assistant, which knows their context and follows them from a personal errand to a work document. Framed that way, two tabs are a bug, because the assistant needs to know both halves of a life to be useful.
That thesis is obviously attractive to the company that owns the surface. It is more ambiguous for everyone else. Enterprise pricing has rested on seats: a per-person licence sold to an employer. A single assistant that a person uses personally and professionally blurs the boundary that made seat pricing legible, and it complicates the question of who pays for usage that is neither clearly work nor clearly personal.
Vertical SaaS tools have a similar problem. A great many of them assumed a clean separation: the general assistant does general things, and the specialised tool does the professional workflow. If the general assistant holds the professional context permanently, a category of tools that existed to hold that context loses its reason to be installed — and the boundary that kept them safe was, in the end, a tab.
The cost of one surface
The risk is not aesthetic. One surface makes permissioning harder: a single workspace has to distinguish between a document a person may share with a client and one they may not, using instructions rather than a container the data cannot leave. Enterprise buyers who spent two years asking for architectural guarantees about isolation will find a merged interface harder to audit, and some of them will say so.
There is a version of this that works: the surface merges while the controls stay separate, with an account-level boundary that follows the person rather than the screen. But that is an engineering claim, not an announcement, and the announcement is all there is so far.
What to watch
The rollout — whether it is a gradual switch or a single date, and what happens to projects built in the old surface. And whether projects and agent features are unified too, because agents are the part of this that actually touches other systems: a merged assistant that can act across both halves of a user's life is a different proposition from one that can merely see them.