OpenAI is retiring ChatGPT Classic app, will soon combine Chat and Work tabs in new app. According to the supplied report, people still using the Classic desktop application on Mac or PC are seeing a banner that says the app will end on January 30, 2027. The retirement is only one part of a broader desktop transition. OpenAI is also preparing to place ordinary ChatGPT conversations and heavier Work tasks inside a single interface, while keeping Codex separate on desktop.
The change affects more than the name of an application. It alters where users chat, create documents, work with files, and delegate larger tasks. A separate change expected to begin in December would replace distinct ChatGPT and Codex usage quotas with a shared pool for Plus, Pro, and Business subscribers. The source offers useful details, but it does not answer every practical question about the interface, quota calculations, or the exact timing of wider availability.
Why ChatGPT Classic is being retired
ChatGPT Classic is described as the original desktop app. It received the Classic name in July 2026, when OpenAI released a new unified application for Windows and macOS. That newer app brings together the familiar chatbot, the Work agent, and access to Codex. Work is presented as an agent capable of building documents, spreadsheets, and presentations, while Codex is OpenAI’s coding tool.
The retirement notice gives Classic users a defined endpoint: January 30, 2027. Until the end of January, the source says Classic will continue receiving model updates and security fixes. Agent features, however, are reserved for the new application. This distinction matters because Classic is not portrayed as immediately abandoned or insecure. It remains supported for a limited period, but it will not provide the newer agent capabilities around which OpenAI is reorganizing its desktop experience.
What happens to existing ChatGPT conversations
The report says conversation history is attached to the user’s account rather than stored only in the Classic app. As a result, migration is described as downloading the newer application and signing in with the same account. The source does not identify a separate conversation-export requirement, nor does it state that users must manually copy chats between applications.
That account-based history should reduce one obvious concern, but the source does not establish that every local preference, shortcut, window setting, or app-specific behavior will transfer. It speaks specifically about conversation history. Users should therefore avoid treating that statement as a guarantee that every aspect of the Classic experience will appear unchanged in the replacement app.
Readers following broader ChatGPT updates should also distinguish between continuity of conversations and continuity of interface design. The conversations may remain connected to the account even when their location, presentation, or surrounding controls change. That distinction became important during the newer app’s early reception.
Why the new desktop app had a difficult start
According to the source, the new app’s launch was not smooth. On Mac, it replaced a native application with an Electron version, described in the report as essentially a web page packaged as an application. Early users reportedly struggled to find conversations in an interface they considered cluttered. These details explain why combining more capabilities did not immediately produce a simpler experience.
OpenAI responded about a week later by adding a Chat/Work selector at the top of the window and a side menu for moving to Codex. The source also reports that Codex grew from five million to ten million users within a few days, attributing that figure to the company. It does not provide an independent measurement or explain exactly how OpenAI counted those users.
OpenAI president Greg Brockman acknowledged during the summer that the situation was “a bit of a mess” and promised that the Work tab would disappear before the end of the year. The forthcoming combined interface appears to address that promise by removing the need to choose between Chat and Work before beginning a task.
How combined Chat and Work conversations are expected to function
In the coming weeks, a small group of users will test a single interface. Within one conversation, a person could chat with ChatGPT and then assign a more substantial task, such as building a website or preparing a presentation. The report says these tasks may use the person’s files and plugins. It does not specify who belongs to the initial test group, how participants are selected, or when the design will reach a broader audience.
Hypothetical example: A user might begin by discussing the outline of a presentation, clarify its intended structure through ordinary messages, and then ask ChatGPT to assemble the presentation as a heavier Work task. This illustrates the type of continuity described by the source; it is not a documented demonstration of the final interface or a promise that every presentation request will be supported.
Hypothetical example: Someone planning a website might discuss its pages in a normal chat and then hand the building task to the agent without opening a separate Work tab. The source explicitly uses building a website as an example of a heavy task, but it does not define the resulting website’s format, publishing options, technical limits, or required permissions.
The intended benefit is contextual continuity. Chat and Work would no longer appear as two separate destinations at the top of the app. A request could develop from discussion into production inside the same conversation. However, the report does not show the final visual design, explain whether users can manually choose a mode, or say how the system decides that a task should use agent capabilities.
Codex will remain separate on desktop
Although Chat and Work are moving together, Codex is not described as joining that same conversation interface. The source says Codex will remain a separate desktop experience. This creates an important boundary: OpenAI is simplifying the relationship between chatting and general task creation, but it is not collapsing every tool into one view.
The report does not explain whether the existing side menu will remain, how switching to Codex will work in the final design, or whether context can move between a ChatGPT conversation and a Codex session. Any claim that chats, files, or instructions will automatically pass between those experiences would go beyond the supplied evidence.
This separation also helps explain why the story belongs to both the AI Tools and AI Trends categories. OpenAI is unifying two forms of work while preserving a distinct coding environment, even as it prepares to connect their usage limits financially through a shared quota.
The shared ChatGPT and Codex quota explained
Starting in December, separate ChatGPT and Codex quotas are expected to be replaced by a shared pool for Plus, Pro, and Business subscribers. Usage would drain that pool at different rates depending on the model selected and the complexity of the task. The source does not provide a table, numerical allowance, conversion formula, or example showing how much quota a particular model or request consumes.
This means the shared quota is clear in principle but uncertain in practice. A subscriber who uses ChatGPT heavily and also relies on Codex would draw from one combined allowance instead of two separate limits. Yet the available evidence does not establish whether the shared total will equal the previous quotas combined, whether account-specific differences will apply, or how users will view their remaining allowance.
Hypothetical example: Imagine a subscriber who spends part of the day on ordinary ChatGPT requests and later opens Codex for a complex coding task. Under the reported model, both activities would count against the same pool, and the more demanding task might reduce it faster. The source does not supply enough numbers to calculate the actual effect, so this example describes the relationship rather than predicting a limit.
OpenAI says most people should not encounter their limits more frequently than they do now. It also says Instant mode will remain unlimited. Those assurances come through the report, but they do not resolve the concerns of users whose activity is divided between an assistant and a coding tool. Some developers are already questioning whether a combined allowance could feel like a reduced subscription without a corresponding price reduction. The source reports that reaction but provides no evidence of an announced price change.
What the evidence does and does not establish
This article is based on the supplied selected evidence source, published on November 3, 2026. That report identifies the Classic retirement date, the planned limited test of combined Chat and Work conversations, the continued separation of Codex on desktop, and the expected December shift toward shared limits.
Several details remain unresolved. The source does not state the precise day in December when shared quotas begin, whether the change will reach all eligible subscribers simultaneously, or how large each shared pool will be. It does not identify the initial testers of the combined interface or provide a general release date. It also does not describe pricing changes, additional plan eligibility, mobile availability, administrative settings, or a final navigation path.
Users can reasonably take the January 30, 2027 Classic end date seriously because it appears in the reported in-app banner. They should be more cautious about assuming exactly when they will see the unified interface. “In the coming weeks” describes an initial test with a small group, not a confirmed universal launch schedule.
What Classic users can take from the announcement
The clearest message is that Classic has a limited future while the newer application is becoming the center of OpenAI’s desktop agent experience. Conversation history is account-based according to the report, and Classic should continue receiving model and security updates through the end of January. The source does not suggest that people must abandon it immediately, but it does establish a deadline and reserves agent functions for the replacement.
The larger question concerns usage rather than installation. Combining Chat and Work could make a conversation flow more naturally from discussion to document, presentation, or website creation. Sharing one quota between ChatGPT and Codex could be less welcome for people who use both extensively. Without numerical limits, no source-grounded comparison can yet determine who benefits or loses capacity.
FAQ
When will ChatGPT Classic end?
The banner described in the source says ChatGPT Classic will end on January 30, 2027. It is expected to continue receiving model updates and security fixes until the end of January, while agent features remain exclusive to the newer application.
Will existing conversations disappear when moving to the new app?
The report says conversation history is tied to the user’s account, not the Classic application. It describes migration as downloading the new app and signing in. It does not guarantee that every app preference or interface detail will transfer.
Are Chat, Work, and Codex all being merged?
No. Chat and Work are expected to operate in one conversation interface during an initial limited test. Codex will remain a separate desktop experience, although its usage allowance is expected to share a pool with ChatGPT for Plus, Pro, and Business subscribers.
When will the shared quota begin?
The source says the shared ChatGPT and Codex pool will begin in December, but it does not provide a precise date. It also does not disclose numerical limits or explain the calculation used for different models and task complexity.
Will Instant mode have a usage limit?
OpenAI says Instant mode will remain unlimited. The supplied report does not add conditions or technical details, so broader conclusions about how that promise will work alongside the shared pool would be speculative.
