Codex Absorbs ChatGPT: What OpenAI's July 9 Reorg Actually Ships

Sixteen hours ago, OpenAI shipped the biggest structural change to ChatGPT since the original app launched. Not a new model page, not a research preview, not a benchmark chart — a product merger. The Codex desktop app now is the ChatGPT desktop app, GPT-5.6 quietly powers a new agent called ChatGPT Work, and Codex remains as a dedicated tab inside the unified surface.

TLDR On July 9, 2026, OpenAI merged ChatGPT and Codex into a single desktop application, introduced ChatGPT Work powered by GPT-5.6, and moved inline diff editing plus pull-request review inside Codex itself. The Codex brand survives as the software-development experience. No verified GPT-5.6 benchmark numbers have been published. More than 5 million weekly Codex users, per OpenAI's own count, wake up today inside a rearranged product.

Key Takeaways

• OpenAI officially confirmed the Codex desktop app becomes the ChatGPT desktop app on Windows and Mac, globally, on every plan including Free.
• ChatGPT Work is a new agent powered by GPT-5.6 that OpenAI says can "stay with a project for hours" and turn goals into finished output across apps and files.
• Codex is not deprecated: Sam Altman stated "codex is the core of our new work product" and "codex is not going anywhere."
• Inline code edits within diffs and PR review in the side panel are now inside Codex, tightening the coding loop.
• No official GPT-5.6 benchmark scores are in the launch materials. OpenAI only claims "new highs" without numbers.

What Was Actually Shipped

The launch pieces confirmed by OpenAI and its team members in the first 24 hours:

• Product merger. OpenAI stated "In the ChatGPT desktop app, Chat, Work, and Codex are available on every plan, including Free, and is available globally to download on Windows and Mac. Codex app users can update their app as usual—it will become the new ChatGPT desktop app."
• ChatGPT Work agent. Introduced as "a new agent in ChatGPT powered by Codex and GPT-5.6" that "can take action across your apps and files, stay with a project for hours if needed, and turn a goal into finished work."
• GPT-5.6 release. OpenAI Developers posted "GPT-5.6 is here. Codex is now available inside ChatGPT" and scheduled a Codex team AMA on r/Codex for July 10, 9:30–10:30 AM PT.
• Rollout schedule. Web and mobile ChatGPT Work goes to Pro, Enterprise, and Edu plans on launch day, with Plus and Business following "over the next few days," per OpenAI.
• Inline code editing and PR review. OpenAI Developers confirmed "Edit code inline within diffs" and "Review pull requests in the side panel" as part of the Codex tab.
• Usage milestone. OpenAI stated in the r/Codex AMA post that "more than 5 million people use Codex every week, twice as many as three months ago" and that the team has "shipped 150 features and improvements in that same period."
• Plugin surface. According to ChrissGPT, the updated Codex now shows "a menu for plugins for the ChatGPT app," matching OpenAI's ChatGPT Work landing page claim of "more than 1,400 plugins available."
• Chrome cookie import. Reported by LinearUncle: the Codex in-app browser now supports importing Chrome cookies and passwords, letting the built-in browser inherit signed-in identities.

That is the surface area that landed in one push.

Why the Merger Matters

The strategic reading is straightforward, if you follow the earlier signals from OpenAI's own team. On June 19, Mark Kretschmann described the trajectory as "The @OpenAI SuperApp is progressing: Codex is getting more features from ChatGPT." On June 29, he added that Greg Brockman was explaining plans to "fus[e] ChatGPT and Codex into a single UI" with the Codex app as the base. On July 4, he wrote plainly that "the migration has already started: More and more ChatGPT features are moved into Codex."

That prediction landed on July 9. The Codex desktop app is now the shipping vehicle for OpenAI's consumer AI product, not just its coding tool.

Three practical consequences follow. First, OpenAI is consolidating around agentic UX as the default, not chat. ChatGPT Work is not a mode toggle; it is a separate tab. Second, the coding audience is not being folded into a general-purpose product — it is being invited into a shared surface where the plugin, browser, and computer-use infrastructure Codex already built becomes the substrate for the wider app. Third, the ChatGPT brand persists on the outside while Codex persists on the inside, which lets OpenAI keep enterprise procurement conversations pointed at "ChatGPT" without abandoning developer mindshare.

Not everyone reads it as a large event. 钟二信 argued the change is essentially "adding a floating chat window to Codex" and that the ChatGPT client was underused anyway. That framing is worth holding onto: the underlying model swap (GPT-5.6) may end up mattering more to builders than the surface reshuffling.

What GPT-5.6 Appears to Change

Verified facts about GPT-5.6 remain thin. OpenAI's r/Codex AMA post describes it as reaching "new highs across key coding and agentic benchmarks" without specifying which benchmarks or citing numbers. The ChatGPT Work landing page positions it as OpenAI's "smartest model series for professional work" and names three variants — Sol, Terra, and Luna — that can "navigate ambiguity, adapt as work unfolds, and deliver polished outputs with less prompting."

Those variant names — Sol, Terra, Luna — are the most concrete new terminology to come out of the release, though the landing page does not spell out how they differ or how the router picks between them. Absent an official model card, treat this as unverified segmentation of a single family.

For context on the model track that led here: on February 5, OpenAI shipped GPT-5.3-Codex and described it as "the most capable agentic coding model to date," setting "a new industry high on SWE-Bench Pro and Terminal-Bench." Community trackers put GPT-5.5 at 88.7% SWE-bench Verified and 82.7% Terminal-Bench 2.0. GPT-5.6 succeeds that lineage. Whether it extends the lead against Claude Opus 4.8 (69.2% SWE-bench Pro versus GPT-5.5's 58.6% in the same tracker) is the first question builders should test independently.

The 5.6 label is significant on its own. It signals OpenAI is not yet claiming a numbered generational jump (no GPT-6), which usually implies incremental gains, not architectural change. On the limited evidence so far, GPT-5.6 appears to be a coding-and-agent focused iteration on the 5.x line — but the absence of a published benchmark card is itself a data point.

The Codex Coding Loop Just Got Tighter

Separate from the merger drama, the code-review loop inside Codex is now materially more contained. The relevant confirmed capabilities:

• Inline diff editing. OpenAI Developers confirmed you can edit code inline within diffs, meaning small fixes no longer require jumping to an external editor.
• Side-panel PR review. Same source: pull request review lives in the side panel.
• GitHub review integration. OpenAI's own developer docs at ChatGPT Learn describe how "@codex review" in a GitHub PR triggers a code review that "posts a standard GitHub code review focused on serious issues" and follows repository-specific AGENTS.md guidelines.
• Claude Code plugin. OpenAI's codex-plugin-cc lets Claude Code users invoke Codex from inside Claude with /codex:review and /codex:adversarial-review, plus rescue, transfer, and delegate commands. The plugin repository shows 26.5K stars and Apache-2.0 licensing.
• Record and Replay. Since June 18, Codex on macOS supports turning a demonstrated workflow into a reusable Skill, requiring Computer Use to be enabled. Not available in the EU at launch.
• Codex Security plugin. Greg Brockman announced the security plugin for "deep scans, validating findings, tracing attack paths, building threat models, generating codebase-specific patches for review, and exporting into other tools." OpenAI's Codex Security plugin setup page confirms both Desktop Codex and CLI installation flows.
• Windows ARM builds. Max Weinbach observed that Codex for Windows now has ARM builds — small, but relevant to Copilot+ hardware users.
• Mobile GA. OpenAI Developers announced on June 25 that "Codex in the ChatGPT mobile app is now generally available" with one-to-one device pairing, notifications, goals, side chat, file previews, and inline review comments.

Stacked together, this is the Jessica Wachtel test at The New Stack captured back in May: "Codex fixed it in 3 minutes. It read the issue, traced the bug to three files in the codebase, wrote a fix, added a regression test, and ran the relevant tests." The July 9 changes push more of that loop inside a single window.

Codex vs Claude Code: What the Signal Says

Named comparisons in the bundle mostly point at Anthropic's Claude Code line. Here is how the signal set stacks up, dimension by dimension.

• Latest coding model. OpenAI: GPT-5.6, released July 9, 2026, no public benchmarks yet in the announcement. Anthropic: Claude Opus 4.8, per Morph LLM's July tracker, released May 28, 2026 with 88.6% SWE-bench Verified and 69.2% SWE-bench Pro.
• SWE-bench Verified (pre-5.6). GPT-5.5 at 88.7%, Claude Opus 4.8 at 88.6% — a 0.1-point spread per the Morph tracker. Whether GPT-5.6 widens or closes that gap is unverified.
• SWE-bench Pro (pre-5.6). Claude Opus 4.8 at 69.2% versus GPT-5.5 at 58.6% — a 10.6-point Anthropic lead per the same tracker.
• Terminal-Bench 2.0. GPT-5.5 at 82.7% versus Claude Opus 4.7 at 69.4% — a 13.3-point OpenAI lead per Morph LLM.
• Community verdict on daily use. Nathan Lambert at Interconnects wrote in February that "Opus is ahead in this matchup on usability" while Codex "keeps an edge as a better coding model" for complex situations. Jonathan Fulton on Medium switched to Codex after a head-to-head, citing skill selection, cross-codebase navigation, and computer usage as differentiators.
• Community counter-verdict. A Reddit r/ClaudeCode thread from a Claude Code power user called Codex "really bad for no-coders" and criticized the lack of plan mode, resume, and steering. Read it as a UX complaint, not a capability claim.

Two dimensions are unverified in the signal set: standalone GPT-5.6 API pricing and its context window are not published in the reviewed materials. Claude Opus 4.8's 1M-token context appears in the Morph tracker versus a 200K-token figure cited there for the prior Codex model, but no official GPT-5.6 context claim is in the bundle.

What We Know vs. What We Don't

What we know, with sources:

• ChatGPT and Codex have been merged inside a single desktop app called ChatGPT Codex per 宝玉's post and confirmed by OpenAI.
• ChatGPT Work is powered by GPT-5.6 per OpenAI's announcement.
• Chat, Work, and Codex are available on every plan including Free in the desktop app per OpenAI.
• ChatGPT Work rolls out on web and mobile to Pro, Enterprise, and Edu plans on July 9, with Plus and Business following "over the next few days" per the same OpenAI post.
• Sam Altman confirmed Codex "is not going anywhere" and called it "the core of our new work product" per his post.
• Inline code editing within diffs and PR review in the side panel are now inside Codex per OpenAI Developers.
• More than 5 million people use Codex weekly, roughly double the count from three months prior, per OpenAI's r/Codex AMA post.
• 150 Codex features and improvements shipped in the last three months per the same AMA post.
• ChatGPT Work advertises more than 1,400 plugins per the ChatGPT Work landing page.
• The Codex in-app browser supports Chrome cookie and password import per LinearUncle.
• GPT-5.6 has three named variants — Sol, Terra, Luna — per the ChatGPT Work landing page.

What we don't yet know:

• No published GPT-5.6 benchmark scores on SWE-bench Verified, SWE-bench Pro, Terminal-Bench 2.0, OSWorld, or GDPval — OpenAI claims "new highs" without numbers in the launch materials reviewed.
• No standalone API pricing for GPT-5.6 has been published in the release materials.
• No explicit GPT-5.6 context window is stated in the reviewed sources.
• No official model card for GPT-5.6 is linked from the reviewed materials.
• How Sol, Terra, and Luna differ from one another — capability, cost, speed — is not documented in the sources reviewed.
• Whether the previously EU-restricted features (Record and Replay) become available in the EU under the merged app is not addressed.
• How the merger affects existing ChatGPT plugin developers and existing Codex plugin developers, given the newly unified plugin menu, is not detailed.
• Whether ChatGPT Work's "hours-long" project claim holds under adversarial testing has not been independently verified.

What Builders Should Do Today

Three practical moves for the next 72 hours.

First, update the Codex desktop app and audit whether your existing shortcuts, plugins, and skills still work after the ChatGPT tab appears alongside them. The bulk of the 150 recent features — Record and Replay Skills, Chrome cookie import, mobile GA, PR side-panel review — carried forward, but Mark Kretschmann already flagged a June 25 update where "Computer Use and even the internal browser are now completely broken." Regressions land.

Second, run your own coding evaluation against GPT-5.6 before relying on the "new highs" claim. A single day of head-to-head prompts against your real codebase — not vibe-coded landing pages — will tell you more than any leaderboard. The Reddit r/codex TCP library benchmark is a good template: one-shot a complex, unfamiliar library, then have a second model review the output.

Third, pin the model version and default variant explicitly in any production integration. With Sol, Terra, and Luna as new sub-labels, silent router changes become a real risk. The Kapil Ahuja post on Towards AI already described one lab silently changing reasoning effort and verbosity across a single day, which "made it impossible to separate a model regression from a prompt change." Build the observability now.

The Week Ahead

Three signals worth tracking. Watch for an official GPT-5.6 model card with SWE-bench Pro, Terminal-Bench 2.0, and OSWorld scores — the current lack of numbers is the biggest gap in the launch. Run a real code-review test comparing @codex review against Claude Code's /code-review on a PR of your own before treating either as production-quality. And pin the Codex desktop app version in your team's tooling policy, because a merged Chat + Work + Codex surface means UI regressions in one tab can now break the workflow of a completely different audience.

Building similar agentic coding and AI-assisted workflows? On kie.ai you can try OpenAI Codex, GPT-5.5, and Claude Opus 4.8.