Cloud coding agents have always had a scheduling problem. You describe a task, the agent works for several minutes in a sandbox somewhere, and then it stops and waits for you — to read the diff, approve it, or send it back with corrections. If you sat at your desk for that entire stretch, the cloud part bought you almost nothing. You may as well have run the work locally and watched it finish.

OpenAI putting Codex inside the ChatGPT iOS and Android apps is aimed straight at that gap. The agent keeps running in the cloud; you check on it from a coffee line, a meeting, or the couch. The desk stops being the place the loop has to close.

What moved into the ChatGPT app

Codex here means OpenAI's software-engineering agent — the cloud product, not the 2021 model that shared the name. It connects to a repository, runs each task in an isolated sandbox preloaded with your code, edits files, runs the commands a task needs, and returns a diff for you to review. Until this rollout, that loop lived in the ChatGPT web sidebar and the Codex CLI.

The mobile version carries over the parts that do not need a keyboard. From the ChatGPT app you can:

• Start a task by describing it in plain language
• See active runs and which ones have finished
• Open the diff a run produced and read the proposed changes
• Send a run back with follow-up instructions, or approve it

What you are not doing on a phone is hand-editing code. The mobile surface is built around delegation and review, not typing — and that is the right scope. Describing a task and judging a result both work on a touchscreen; writing and steering code line by line does not. By shipping the agent inside an app developers already keep open, OpenAI also skipped the install step every standalone coding tool has to fight through.

Treat the mobile app as a triage surface, not a development environment. The highest-value mobile actions are starting a run before you leave your desk and clearing a review queue while you are away — not trying to drive a full feature from your phone.

Why a phone changes the workflow more than it looks

The headline is not "code from a beach." It is that an asynchronous agent only pays off when triggering and reviewing are both cheap. A cloud agent you can reach from one machine is just a slower local agent. Make the two cheap actions — kick off, check back — available everywhere, and the economics change.

Think about how a normal day fragments. You have a ten-minute gap before a call, a commute, a stretch of waiting at an appointment. None of that is long enough to load a feature into your head and write it. All of it is long enough to describe a contained task — "add input validation to the signup form and a test for the empty-email case" — and let the agent run while you do something else. You come back to a diff, not a blank editor.

It also changes how you batch work. Because each Codex task runs in its own sandbox, you can have several in flight at once. The bottleneck stops being how fast the agent writes code and becomes how fast you review what it produced. A review queue you can chip away at in two-minute increments is a queue that does not pile up until Friday afternoon.

Mobile also gives the agent a way to interrupt you. A run that finishes, fails a test, or needs a decision can surface as a notification instead of sitting silent in a browser tab you already closed. That turns the agent from something you have to remember to check into something that tells you when it needs you — roughly the difference between three review cycles in a day and thirty.

The honest limitation: this only helps for work that decomposes into self-contained, well-specified tasks. Vague instructions produce diffs you cannot judge from a phone, and ambitious refactors still need a real editor and a test run in front of you. The mobile app rewards developers who already write tight task descriptions and offers little to hand-waving.

A small screen makes it tempting to approve a diff you only skimmed. A coding agent will confidently produce changes that pass a glance and fail in CI. Before you tap approve on mobile, confirm the run included a test step and that you have actually read the parts of the diff that touch logic — not just the line count.

Where this leaves Cursor and Claude Code

Each major coding agent has staked out a different home surface. Cursor is editor-first: the agent lives inside an IDE where your edits and the agent's edits share one window, which suits tight, interactive work and does nothing for you away from the machine. Claude Code is terminal-first: it runs where your shell and scripts already are, which fits developers who live on the command line. Codex is now ChatGPT-app-first, and that app is already on the device in your pocket.

That is a real distribution advantage. The ChatGPT app sits on hundreds of millions of phones, so OpenAI did not have to sell developers a new tool — it added a capability to one they open for other reasons. The trade-off is depth: a chat app wrapped around an agent will not match a dedicated IDE for the moment-to-moment work of writing and steering code.

The realistic outcome is not a single winner. It is that your desk tool and your away-from-desk tool stop being the same product. You might steer a hard refactor in an editor at your desk, then use a mobile agent to keep small, well-defined tasks moving for the rest of the day.

If your day is mostly deep work at one machine, an editor-resident agent will still carry most of the load. If it is fragmented across meetings and travel, a coding agent inside the ChatGPT app turns dead time into a working review queue. Most developers will end up using both — for different hours of the same day.

Originally published at pickuma.com. Subscribe to the RSS or follow @pickuma.bsky.social for new reviews.