Codex Just Joined ChatGPT. That Changes How Your Whole Team Builds Software.

On 9 July, OpenAI stopped treating coding like a separate activity. The standalone Codex app is gone. In its place: a single ChatGPT desktop app with three modes — Chat, Work, and Codex — sharing the same plugins, the same files, the same browser, and the same GPT-5.6 engine underneath. The old ChatGPT desktop app has been quietly renamed "ChatGPT Classic" and left in the corner.

If you run a team, here's why this week matters more than the model release. Your operations people, your finance team, your marketing leads — the ones who'd never open a terminal — now sit one click away from the same coding agent your developers use. The barrier between describing what software should do and actually building it just evaporated.

Three modes, one app, no friction

The desktop app now organises itself around what you're trying to accomplish rather than what tool you're supposed to use.

Chat handles the quick stuff — questions, brainstorming, drafting. Work takes on longer jobs: research across your connected apps, building finished spreadsheets and slide decks, running multi-hour projects that carry context across steps. Codex remains the dedicated coding workspace, now with inline diff editing, PR review in a side panel, faster Computer Use, and support for multiple repositories in one project.

The difference is that your marketing manager can start in Work mode describing a campaign brief, have the agent pull data from your CRM and Slack, produce the assets, then hand off to Codex when someone needs to build the landing page. Same app. Same plugins. Same model choosing between Sol, Terra, and Luna depending on task difficulty. Nobody had to learn what a repository is.

Five million people already use Codex weekly. OpenAI says more than a million of them use it for work outside software development. That number was climbing before the merger. It'll accelerate now that Codex sits in the same app where everyone already spends their day.

Custom instructions got real

A smaller change landed on 15 July, and it's easy to miss if you're focused on the desktop app headlines. The custom instructions limit jumped from 1,500 characters to 5,000 for paid plan users.

Fifteen hundred characters is a long text message. Five thousand is a proper briefing document. For teams, this matters enormously. You can now encode your organisation's tone, your compliance guardrails, your preferred output formats, and a worked example of what "good" looks like — and have it apply across every Chat, Work, and Codex session.

This is the plumbing that makes the three-mode app actually usable at scale. Without it, every team member gets a slightly different agent. With 5,000 characters of shared instructions, your finance department's Work sessions and your engineering team's Codex sessions pull from the same rulebook. Consistency stops being a hope and starts being something you configure.

What the ops team can now do

I want to be specific about what changes for non-technical staff, because the headline sounds abstract. Here's the actual shift.

Before the merger: if your operations lead wanted a dashboard tracking supplier performance across three systems, they had two options. Ask IT (and wait six weeks), or cobble something together in Excel that fell out of date the moment it was shared.

Now: they open the ChatGPT desktop app in Work mode, connect the relevant plugins (SharePoint, email, the ERP), and describe what they want. Work pulls the data, builds the dashboard as a ChatGPT Site that updates as source data changes, and shares the link. If the dashboard needs a custom integration, they don't file a ticket. They switch to Codex mode, describe the connector in plain English, and the agent writes it.

The person who couldn't read a line of Python an hour ago just shipped a working internal tool. The developer on your team didn't get interrupted. Everyone's working at the top of their licence.

That's the promise, at least. The reality will be messier, especially in the first few months while Work and Codex don't fully sync across cloud and desktop sessions. Chat conversations carry across devices. Work and Codex threads currently don't. If you're mid-project on desktop and want to check progress from your phone, you'll hit a wall. OpenAI says unification is coming. For now, pick one surface per project and stick to it.

The everything-app is also the everything-lock-in

There's a tension here that team leads should sit with for a minute.

OpenAI has built the gravitational centre of software creation. Chat, Work, and Codex in one app. Plugins connecting to your CRM, your email, your file storage, your calendar. Sites that turn any output into a shareable web app. A built-in browser that pulls in web-based tools. Scheduled Tasks that run even when you're away.

This is brilliant for getting things done. It's also brilliant for OpenAI. Every plugin you connect, every Site you publish, every workflow that spans Chat-to-Work-to-Codex — that's switching cost. Real switching cost. The kind that makes your finance team groan if someone suggests evaluating a competitor.

I'm not saying don't use it. Five million weekly Codex users aren't wrong. But the smart play is to treat the desktop app as your execution layer while keeping your actual software — the stuff customers depend on, the internal portals your suppliers log into — on platforms you control. A no-code platform that abstracts away the model provider entirely. Stacker, Bubble, whichever. Something where the application lives independent of who won this month's AI race.

OpenAI's doing what any company with distribution would do: making their app the place where work happens. Your job is to make sure your organisation's software assets don't live and die with one vendor's desktop application.

The takeaway

The Codex merger isn't a developer story dressed up as something broader. It's the opposite. It's a workplace story that happens to include coding.

For the first time, the same application that handles your team's daily questions and document creation also handles software development. That collapses the distance between "someone should build that" and "someone just built that" to roughly zero. The people who benefit most aren't the engineers who already had Codex. They're the operations leads, the analysts, the project managers who now have a coding superpower they didn't need to install separately.

The custom instructions expansion makes this actually governable. The three-mode design makes it approachable. The plugin ecosystem makes it connected.

Just keep your crown jewels somewhere portable. The everything-app is wonderful until you need to leave it.