ChatGPT Work vs Codex: What Actually Changes (Help Center + r/codex Explained)
OpenAI merged ChatGPT and Codex into one desktop app with Chat, Work, and Codex modes. explainx.ai maps official help docs, shared usage limits, cloud vs local sync gaps, and vs Claude Cowork from r/codex developer reports.
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.
"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.
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.
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.
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
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.
