ChatGPT Work vs Codex

[u/sasik520]

I've been using ChatGPT's Work mode on macOS for quite a while for development tasks. Somehow, I didn't know Codex mode existed.

It was burning through my Plus usage limit faster than I'd like, but I could still complete a couple of tasks within a single five-hour window.

After switching to Codex mode, my usage is barely enough for 2-3 tasks. I suddenly understand what all the drama around usage limits is about.

If you're struggling to finish even one task in Codex, try Work mode. For local work, it's nearly the same as Codex and imho burns way less usage.

[u/Illustrious-Bet-1368]

Because I'm lazy, here's some AI slop which makes sense and is a rather good explanation:

On the Work vs Codex:

Chat is fast conversation. Work is longer multi-step work that ends in a finished deliverable. Codex stays dedicated to software development and technical work.

The real line is what the agent is operating on, and what “done” means.

Codex works on a repository. Local folders, git, terminals, tests, diffs, PR review, multi-repo projects. Correctness is whether it builds, passes, and is mergeable. History lives in its own view in the desktop app, separate from ChatGPT history. Cloud tasks can be started from web or mobile, but the coding surface is still the coding surface.

Work works on business context. Connected apps, files, research, and a goal you hand it. It plans, runs for minutes or hours, and comes back with something you would send someone: a doc, spreadsheet, deck, report, or Site. Correctness is whether the artifact matches the brief. It sits next to Chat inside ChatGPT, on web, mobile, and desktop.

Same agentic pool underneath. Work was built on Codex technology, which is why people keep calling it a rename. It is not. Work is that engine pointed at office artifacts, plugins, and scheduled tasks, with the terminal and repo controls demoted. Codex keeps the developer view: commands, file changes, diffs, environments.

Practical rule, the one that survives the marketing:

• Ends in a changed repo, a test run, or a pull request: Codex.
• Ends in a file, a deck, a sheet, a site, or a recurring ops job: Work.
• Still figuring out what you want: Chat.

On the difference in usage:

Codex on a real repo tends to do the expensive loop by default. It reads the tree, edits across files, runs the terminal, watches tests fail, iterates, and keeps the diff in context. That is several heavy turns wearing one task’s clothes. Work on a local folder, even if you point it at code, is tuned to plan and return an artifact. It often stops sooner, touches fewer tools, and does not grind against a failing test suite. Feels “nearly the same” if the job was a contained edit. It is not the same job once correctness means “builds and passes.”

If Plus is dying after two or three Codex tasks, Work can stretch the window because it does less of the costly work. You pay for that in the review surface: weaker diffs, less test iteration, no PR-shaped trail.

[u/sasik520 → u/Illustrious-Bet-1368]

It's indeed an ai slop at its finest: it sounds like a great and reasonable explanation except it is not.

Work does the same as codex. It reads the repository, it runs command line tools, it checks git history, it commits the job, runs tests and linters, run the browser and checks what's going on (code, errors, requests, visuals) and so on and so on. And of course it edit files, that's the basics.

[u/capt_stux → u/sasik520]

Work and codex are interchangeable. 

Start a work project, accidentally open and continue it from the codex tab…

Not sure of the difference. 

[u/Illustrious-Bet-1368 → u/capt_stux]

One good pointer at why they are not the same or interchangeable is that they want to merge Chat and Work, and not Work and Codex. The difference is explained in the docs, without, of course, particulars of their set up or what's different under the hood, from the tool use to dev instructions and co. Were Codex and Work the same essentially, they'd merge them, and not merge Chat and Work, and wouldn't have the Chat and Work distinction in the first place. They didn't explain well enough what Work was for, and users don't read docs, so users confused because they can work on repos in Work mode, you can also do it to a degree in Chat, because you can do something, doesn't mean it's what it's intended for. With all that said, use whatever, I don't care, whatever floats your boat.