OpenAI merges ChatGPT with Codex

OpenAI is reorganizing the teams behind ChatGPT, Codex and its developer-facing API into a single product organization led by co-founder Greg Brockman, according to reports published on May 15 and May 16. WIRED reported that OpenAI confirmed Brockman had officially taken over product strategy, while TechCrunch and other outlets said the company was merging the three product lines into one structure. The move comes as OpenAI’s own product pages already show increasing overlap between its chat, coding and developer offerings. OpenAI says Codex is “powered by ChatGPT,” available across desktop, IDE, terminal and cloud surfaces, and included in ChatGPT plans while also being accessible with API credits. OpenAI has not, in the sources reviewed, published a standalone public blog post announcing the reorganization. (wired.com) But the company’s recent releases show it has been tightening the links between ChatGPT and Codex in public-facing products over the past week. ### Why would OpenAI put ChatGPT, Codex and the API under one team now? May 16 reporting from TechCrunch said the reorganization would place Brockman in permanent charge of product strategy while top executive Fidji Simo remained on medical leave. (openai.com) WIRED reported the company was unifying ChatGPT and Codex into one core product experience. (openai.com) The Information, in a brief cited by search results, said OpenAI was combining the teams working on ChatGPT, Codex and the API into one organization as part of a more streamlined app strategy. That aligns with how OpenAI now presents Codex: not as a separate lab experiment, but as an agent that follows users across ChatGPT, desktop tools and developer workflows. (techcrunch.com) ### What does Codex look like inside OpenAI’s product stack now? OpenAI’s developer documentation says “every ChatGPT plan includes Codex,” while API users can also access it with API credits. The same quickstart page lists the Codex app, IDE extension, CLI and cloud access at chatgpt.com/codex, showing that the product already spans both consumer and developer channels. (theinformation.com) OpenAI’s Codex landing page describes the app as “the command center for agentic coding” and says the same agent works “everywhere you build.” The company also says Codex can handle code generation, code review, debugging and repetitive engineering workflows. May 14 product notes added another link between the two brands: OpenAI said Codex was coming to the ChatGPT mobile app in preview, allowing users to monitor and approve coding tasks from a phone while work continued on laptops or remote environments. (developers.openai.com) OpenAI said more than 4 million people now use Codex every week. ### What problem does a unified structure solve? (openai.com) OpenAI’s public materials show the same account, model family and interfaces now stretch across chat, coding and API use cases. When one company sells a chatbot, a coding agent and developer access to the same underlying systems, separate product organizations can create duplicated controls, inconsistent features and different user expectations; that is an inference from the overlap shown in OpenAI’s own docs. (openai.com) Greg Brockman’s reported language points in the same direction. Search-result summaries of the memo said he told staff OpenAI would invest in “a single agentic platform” and merge ChatGPT and Codex into one unified experience. ### What can users watch for next? May 15 and May 14 entries on OpenAI’s news page show the company is still shipping changes to ChatGPT and Codex on a near-daily basis. (openai.com) The most recent listed items include “A new personal finance experience in ChatGPT” on May 15 and “Work with Codex from anywhere” on May 14. OpenAI’s product and developer pages are the clearest places to watch for the next visible signs of the reorganization. (thenextweb.com) Those pages already show Codex distributed through ChatGPT plans, API billing and cross-device workflows, and any deeper merger of the products is likely to appear there first. (developers.openai.com) (openai.com)