OpenAI did not ship a new model. It shipped a new harness — and renamed the Codex desktop app ChatGPT.
The ChatGPT Work and Codex help article (updated ~July 11, 2026) splits the product into three experiences: Chat, Work, and Codex. A 60-comment r/codex thread from the same week asks the question every builder has: what actually changes in the backend?
Short answer from the community: same GPT-5.6 agent, shared agentic quota, different prompts and UI defaults. Long answer below — with official docs, developer reports, and vs tables for Cowork, Classic, and cloud vs desktop.
Update — July 27, 2026: ChatGPT Work gains thread orchestration / sub-agent tools for coordinating work across phone conversations — Altman’s “Work undersells it” mobile demo. Full decode: ChatGPT Work thread orchestration.
Update — July 28, 2026: Companion on the viral 9-person trip + Sites + Gmail prompt and “personal AI” framing: Sam Altman’s ChatGPT Work trip demo.
Update — July 24, 2026: ChatGPT Voice on desktop — GPT-Live steers Work/Codex agents by voice (macOS Appshots, quotas = standard agent buckets). Same day security note: Zenity AgentForger — one ChatGPT link could forge a Workspace Agent (patched Jun 2026).
Update — July 23, 2026: Tibo Sottiaux says July 24 is "feeling codexy." Our pre-release guide separates the confirmed Codex teaser from Linux, voice, model, UI, and reset speculation.
Update — July 21, 2026: jcode supports OpenAI/Codex OAuth and session resume from Codex — an alternative terminal harness if ChatGPT app mode split frustrates you; RAM benchmarks in that post are author-run, not OpenAI-verified.
Update — July 15, 2026: Tibo reported 8M active users across Codex + Work — growth timeline and limit resets.
TL;DR — Chat vs Work vs Codex
| Mode | Official purpose | Where it runs | Burns agentic quota? |
|---|---|---|---|
| Chat | Questions, brainstorm, quick help | Desktop Quick chat · web · mobile | No (per community) |
| Work | Research, docs, slides, reports, Sites | Web · mobile · desktop | Yes — same pool as Codex |
| Codex | Code, tests, repos, terminals | Desktop only (+ mobile Remote tab) | Yes |
| Question | Answer |
|---|---|
| Different models? | No — same agent family; framing differs |
| Different limits? | Work + Codex share limits · Chat separate |
| Can I keep using Codex as before? | Yes — select Codex in top-left switcher |
| Why does Work feel identical? | Modes switch mid-thread · skills/terminal work in both |
| Biggest pain point? | Cloud vs desktop history does not sync at launch |
What OpenAI officially says
From the Help Center article:
"ChatGPT includes Chat, ChatGPT Work, and Codex. Chat handles questions and conversation. Work takes on longer research and creates finished materials. Codex remains the dedicated agent for software development and technical work."
Rollout note: Work is gradually rolling out to eligible paid accounts — if you do not see it yet, availability is still expanding.
Choose an experience
| Mode | Use when you want… |
|---|---|
| Chat | Fast Q&A, search, brainstorming |
| Work | A document, spreadsheet, presentation, report, or Site |
| Codex | Write/debug code, run tests, review PRs, work in a repo |
Usage: Work follows the same structure as Codex. The Codex pricing page explains included usage; examples are coding-oriented, so Work burn varies by task length and tool use.
ChatGPT Work vs Codex — technical breakdown
This is the comparison r/codex wanted. OpenAI's marketing split is clean; the implementation is messy.
Official surface differences
| Dimension | ChatGPT Work | Codex |
|---|---|---|
| Primary output | Deliverables (docs, decks, reports, Sites) | Code, diffs, tests, repo changes |
| Web/mobile | ✅ Selectable mode | ❌ Not selectable (Remote tab only) |
| Desktop | ✅ Mode switcher | ✅ Mode switcher |
| Local files | Desktop Work with folder permission | Repos, terminals, dev tools |
| Cloud execution | Web/mobile Work runs in cloud | Desktop local + cloud tasks |
| Usage billing | Shared agentic pool | Shared agentic pool |
What developers found under the hood
Multiple r/codex reports converge on the same model:
| Layer | Work profile | Codex profile |
|---|---|---|
| Core agent | Same GPT-5.6 Codex-class agent | Same agent |
| System prompt | General-purpose · less technical tone | Code-first · repo-aware |
| Workspace | Generated folder under Documents/Codex · projectless | Git worktrees · repo roots · coding controls |
| Connectors | Slack, Drive, office-style outputs (community) | Terminals, CI, IDE extension, CLI |
| Skills | ✅ Work in both modes today | ✅ Same skills |
| Terminal | ✅ Still executable in Work | ✅ Native |
| Mid-thread switch | ✅ Toggle anytime | ✅ Same conversation can flip modes |
RouterDon (r/codex): "it's the same GPT 5.6 codex agent underneath, Work just points it at docs and research and hides the code while sharing the same usage limits so the split is framing not a different model."
Certain-Way6763 had the agent inspect its own environment:
Work frames a task as general-purpose, projectless work… Codex is the project/code-first profile: Git worktrees, coding controls, local-versus-cloud execution.
explainx.ai read: OpenAI is productizing two personas on one runtime — like Anthropic's Cowork vs Code split — before the UX catches up.
Chat vs Work vs Codex — usage limits (what burns quota)
The limit merge is the real product change — not the mode names.
Paid ChatGPT agentic usage (July 2026)
├── ChatGPT Work tasks ─┐
├── Codex desktop tasks ─┼─► SHARED weekly / agentic pool
├── Codex cloud / Remote ─┘
└── Quick Chat (Chat mode) ──► Separate ChatGPT.com-style quota
| Activity | Counts against Codex/Work pool? |
|---|---|
| Long Work research run | Yes |
| Codex multi-agent refactor | Yes |
| Scheduled automations (either mode) | Yes |
Quick chat side panel (Ctrl+Alt+N) | No (community consensus) |
| "More details" on highlighted Codex text | No — opens Chat thread |
Kombatsaurus (r/codex): "The purpose is to slowly combine your ChatGPT Chat usage with your Codex usage limits." That has not fully happened — Chat still routes around agentic burn via Quick chat and side panels.
Launch-week context: Tibo removed the 5-hour cap temporarily and denied Sol thinking-budget nerfs while traffic hit 7M users — Work + Codex share that stress.
Cloud vs desktop — the sync mess
Official help center language that explains most r/codex frustration:
| Surface | Behavior at launch |
|---|---|
| Work on web/mobile | Cloud only · syncs across cloud surfaces |
| Work on desktop | Can use local files with permission |
| Cloud → desktop Work | Does not appear in desktop Work |
| Desktop Work threads | Stay on that computer |
| Codex desktop tasks | Not on web chat history |
| Mobile Remote tab | Access some desktop Codex tasks · not full history |
| Chat (Quick chat) | Syncs web ↔ desktop app |
Active-Lychee-8617: "they literally copied claude cowork and the mess of desktop vs cloud… really unintuitive."
Practical rule until OpenAI fixes sync:
- Start cloud Work on web if you need cross-device continuity
- Start desktop Codex if you need repos — accept it stays local
- Do not assume browser Work threads appear in the desktop sidebar
How to switch modes (official UI)
Desktop (ChatGPT app — formerly Codex)
| Action | How |
|---|---|
| Work | Click ChatGPT Work top-left |
| Codex | Click ChatGPT Codex top-left |
| Chat | Quick chat button in left nav · Ctrl+Alt+N mini window |
Mobile
| Action | How |
|---|---|
| Work / Chat | Dropdown at top (Chat or Work) |
| Codex | Remote tab for supported desktop tasks only |
ChatGPT Work vs Claude Cowork
The mapping developers use on both Reddit threads:
| OpenAI | Anthropic | Role |
|---|---|---|
| ChatGPT Codex | Claude Code | Developer agent · repos · terminals |
| ChatGPT Work | Claude Cowork | Knowledge work · deliverables · connectors |
| Quick Chat | claude.ai chat | Fast unmetered-style conversation |
Feature vs table
| Dimension | ChatGPT Work | Claude Cowork |
|---|---|---|
| Target user | Non-dev office work + some technical users | Knowledge workers · legal · ops |
| Dev tooling | Weak in Work · use Codex mode | Weak — use Claude Code |
| Connectors | Drive, Slack (community) · expanding | Knowledge Work Plugins |
| Desktop agent | Unified ChatGPT app | Cowork desktop |
| Security posture | Foreground Codex tasks · computer use | CVE history |
| Quota coupling | Work + Codex merged | Cowork + Code separate buckets |
| Cloud/local split | Broken sync at launch | Similar confusion reported |
When to pick Work over Cowork: You already pay for ChatGPT Pro/Business, want GPT-5.6 Sol on office deliverables, and will drop to Codex mode for the same session's code follow-up.
When to pick Cowork: Anthropic stack, Fable 5 through July 19, or connector ecosystem matters more than OpenAI's unified quota.
ChatGPT Work vs Codex — when to use which
| Task | Use Work | Use Codex |
|---|---|---|
| Write a thesis chapter | ✅ Default prompts lean research | ⚠️ Works but code-biased |
| Build a SwiftUI app | ❌ | ✅ iOS guide |
| Redline a client contract | ✅ (community: lawyers on Work) | ✅ Same agent, worse defaults |
| Git worktree parallel agents | ❌ | ✅ Native |
| Spreadsheet + Slides deliverable | ✅ Intended path | ⚠️ Overkill |
| You just want old Codex | ❌ Ignore Work | ✅ Stay in Codex mode |
OP Constant-Software967 conclusion matches most builders: "for now I'll probably just stick with Codex, ignore these features, and wait to see how it develops."
ChatGPT Classic vs new unified app
| App | What it is |
|---|---|
| ChatGPT (new) | Former Codex app · Chat + Work + Codex modes |
| ChatGPT Classic | Old ChatGPT desktop app · full chat experience |
| Browser chatgpt.com | Still the reference for Deep Research, full Projects |
vg5unk: "feels like they just updated Codex and killed the ChatGPT app." Update: Classic still exists — naming moved, not removed.
If Chat inside the new app feels limited, you are not alone — peakedtooearly: "the chat window is a bolted on afterthought." Browser or Classic remains better for pure conversation.
Power user tricks (from r/codex)
1. Side chat without burning Codex quota
Inside a Codex task, highlight text → More details → opens Chat window with focused answer. Does not debit agentic usage (multiple confirmations).
2. Add side chat context back to Codex
Highlight → Add to task pipes Chat context into the agent thread.
3. MCP workaround (experimental)
fruitydude: Route unmetered Chat through local MCP servers for file access — effectively "Codex without usage limits" if tooling is solid. High setup cost; not official.
4. Avoid accidental Work burns
Active-Lychee-8617 started a long task in Work by mistake. Pin Codex in the switcher if you are a developer.
What OpenAI got wrong (launch feedback)
Tibo admitted OpenAI "didn't get everything quite right" — covered in July 12 limit post:
| Complaint | Status |
|---|---|
| Hidden chats / projects | Sidebar fix promised |
| Codex deprecation fear | Tibo: Codex stays |
| 5-hour + weekly double cap | 5h removed temporarily |
| Work/Codex indistinguishable | Documentation gap — this post |
| Cloud/desktop history split | No fix date |
| Model picker overload (50 options) | iOS Work reports · ongoing |
What developers should do now
- Developers: Default to Codex mode — ignore Work until sync improves
- Knowledge workers: Try Work on web for deliverables · verify quota in
/usage - Quota conservation: Use Quick chat + More details for explanations · agent for execution
- Cross-device: Assume no sync between cloud Work and desktop Work
- Compare harness: Codex vs Claude Code if evaluating Anthropic
- Long runs: Loop engineering + GPT-5.6 Sol limits
What to watch next
| Signal | Why |
|---|---|
| Desktop sidebar return | Tibo "next week" promise |
| Work ↔ desktop sync | Biggest UX blocker |
| Separate chat histories | Would make mode split real |
| Quota tooltip update | Should name Work explicitly |
| ChatGPT Classic sunset? | "Classic" naming worries power users |
| 7M user banked reset | July 14 fleet grant |
Related on explainx.ai
- ChatGPT Work thread orchestration — mobile July 26
- Sam Altman’s ChatGPT Work trip demo — personal AI
- ChatGPT AgentForger — Workspace Agents CSRF
- ChatGPT Voice on desktop — GPT-Live for Codex & Work (Jul 23, 2026)
- Codex Micro — kbd-1.0 Work Louder hardware (Jul 15, 2026)
- OpenAI Codex plugin for Claude Code — /codex:review and /codex:rescue
- ChatGPT drops 5-hour limit — Work + Codex quota
- GPT-5.6 Sol thinking budget + banked resets
- Codex vs Claude Code — developer verdict
- Codex computer use vs Claude Cowork
- Is Claude Cowork safe?
- Claude vs ChatGPT for work professionals
- Codex slash commands reference
- GPT-5.6 vs Fable 5 — frontier comparison
- macOS Codex malware alert — false positive fix
Sources: OpenAI Help — ChatGPT Work and Codex · OpenAI Codex product page · r/codex — Work vs Codex thread · The Decoder — ChatGPT Work launch fixes
Mode behavior reflects OpenAI Help Center text and r/codex reports as of July 13, 2026. Rollout is gradual — verify which modes appear in your account before changing team workflows.