Codex became ChatGPT — the real upgrade is the work system

Recently I opened Codex and found that, after an upgrade, it had become ChatGPT.

At first I was a little lost: Codex? Work? Chat? Task?

After looking into it, I learned ChatGPT is playing a bigger game.

Three entry points

Chat is more like the conversation entry: asking questions, editing copy, sorting out ideas.

Work is more like the delivery entry: turning material into briefs, reports, spreadsheets, slide decks, PRDs.

Codex is more like the engineering entry: reading code, changing repos, running tests, debugging, reviewing PRs.

The real change

We used to treat ChatGPT as a chat box. Now it’s starting to become a work system: a place to chat, a place to make deliverables, a place to handle code.

Work and Codex aren’t replacing each other. They overlap in capability, but their default stance differs.

Work by default makes “results for people to read.”

Codex by default pushes “changes inside a system.”

One thing that’s easy to overlook

Memory settings are often part of how I choose between tools and modes, too.

Work uses the memory in your ChatGPT account.

Local Codex has its own local memory, geared more toward development tasks and the habits of projects on your machine.

Suggestions

If you just want to talk something through, use Chat.

For organizing material, writing documents and making reports, use Work.

To change a website, change code or deal with a repo, use Codex.

Put long-running topics in a Project.

Don’t rely on memory alone for important rules; better to write them into instructions.

Let’s see whether ChatGPT goes from a “chat tool” to a “workbench.”

Chat is for thinking things through.

Work is for turning them into deliverables.

Codex is for getting the system right.

*If you want to try Work, start with a small decision.

Don’t throw a huge project at it right away. Pick a real but low-risk question, like “should I apply for this job,” “should I buy this course” or “how should I plan this weekend.” Give it two links, a bit of background and a few constraints, and have it produce a one-page decision brief: goal, options, recommendation, risks, next steps. If it can turn scattered information into a draft you’d be willing to keep editing, you’ll see what Work is for: it isn’t one more chat entry point, but a step that pushes conversation toward a deliverable.