Your Phone Is Now a Dev Tool. Kind Of
OpenAI just put Codex in your pocket — but let's be real about what that actually means.
Real John here - This week is me coming back from vacation. I wrote this entire thing on mobile (just to see) and truthfully, I got the content down fine, but the formatting sucked. I had to go to the desktop to clean up the title, subtitle, headings, and bold/italics. All in all, it is good, but not great. What is great is what I was able to do with codex today. I rebuilt my entire website (again) here: https://startupsandcode.com/ all from my phone. I created a new branch viewed a preview deployment, and even pushed to vercel for the preview. It was amazing. It created its own project initially, but with further instructions, it took the existing project, identified the architecture, and created a new branch and created a PR (which I did review on a desktop, not mobile). It was crazy. There is no limit on what you can develop on, and how fast you can go… but be careful, it can do things you don’t want it to do and you may never know, unless you pay close attention. The “approve all” is easy but also can have some serious consequences… ok, let’s get into it - Ace of Diamonds, if you know you know (first ace in a while, seems like a good omen). Here’s this week’s newsletter.
I was on the subway the other day — 1 train, naturally packed — and I thought about a bug I needed to fix in a running Codex session. Couldn’t do anything about it. Had to wait until I got home, sat down, opened the laptop. Classic developer problem. You are never more productive than when you’re away from your desk.
OpenAI heard that complaint. On May 14th, they officially rolled Codex into the ChatGPT mobile app on iOS and Android, available in preview across all plans — including free. And the developer world immediately lost its mind about it.
I’m excited too. But let’s pump the brakes for exactly one minute before we declare the death of the desktop.
What Codex Mobile Actually Is
Here’s what OpenAI shipped: remote control for your desktop Codex session.
That’s it. Your phone is not running the code. Your phone is not spinning up environments. Your Mac — note the word Mac, Windows is “on the roadmap” — is doing all the heavy lifting. The mobile app is the control surface. You can review diffs, approve commands, switch models, kick off new tasks, and monitor what your agent is doing in real time.
It’s basically a dashboard with approval buttons. A very smart, very useful dashboard with approval buttons.
The workflow OpenAI pitched is exactly right: “Start something from a computer at home and then go out to the coffee shop and approve the final output over your matcha.” That’s the use case. You fire off a refactor, walk the dogs, and your phone buzzes when Codex needs a decision. You say yes or no. The agent keeps going.
That’s genuinely useful. I’m not being sarcastic. As someone who builds things in the margins of a full-time engineering executive role, asynchronous agent control changes the math on what I can ship in a week.
But — and this is important — this is management, not development.
The Shift Nobody Is Naming
Here’s what’s actually happening here, and nobody in the press release is saying it directly.
We are entering the era of async development. The mental model we’ve had for 30 years — sit down, type code, see result, iterate — is being replaced by something that looks a lot more like being a project manager for an AI team.
You write the prompt. You set the direction. You review the output. You approve or redirect. The execution is happening in the background, while you’re on the subway, walking the dog, sitting in yet another meeting that could have been an email.
I’ve been building on Codex. I’ve also been deep in Claude Code, which, for the record, Anthropic shipped remote control for back in February — three months before OpenAI caught up. Both tools are converging on the same pattern: the agent works, you supervise.
The practical question is no longer “can I code on my phone?” The answer to that has always been “technically yes, but it’s miserable.” The real question is now: how much do you trust your agent?
Because approving a diff on a 4-inch screen without reading every line means you are trusting the agent made the right call. Sometimes it will. Sometimes it will confidently remove something important. And you approved it on a phone, between stops on the 1 train.
How to Actually Use This Well
Here’s my honest take on when mobile Codex is a superpower and when it’s a trap:
Use mobile for:
Monitoring long-running tasks you already kicked off and understood
Quick approvals on small, isolated changes (a single function, a config update)
Starting new tasks you’ve pre-thought through and can describe precisely in a voice note or quick prompt
Staying unblocked while you’re away from the desk — the friction of “I’ll do it when I get back” kills momentum
Don’t use mobile for:
Approving large refactors you haven’t reviewed carefully
Debugging anything where you need context across multiple files
Making architectural decisions in a Slack message format while distracted
The pattern that works: think at the desk, supervise from the phone. Your laptop is where you set up the task clearly and give the agent enough context to run. Your phone is where you keep the task alive when life happens.
The Part That Still Matters
I’ll say this plainly: the most important skill in 2026 is not knowing how to code. It’s knowing how to direct code. Knowing what you’re asking for. Knowing when the output is wrong even if it looks right. Knowing the difference between “the agent finished” and “the agent finished correctly.”
The mobile release doesn’t change that. If anything, it amplifies it. You’re now approving work at 30 second intervals between meetings. Your judgment — built from actually understanding what your code does — is the last line of defense.
I built Cash Critters using these async patterns. I’m not chained to a keyboard for hours anymore. But I know the codebase. I know what a bad diff looks like. That knowledge is what makes the workflow actually work.
The phone is just the remote. You still have to know what you’re controlling.
Go build something amazing.
John Mann is the founder of Startups and Code LLC, a software engineering executive, and the guy who built Cash Critters for $50/month because constraints are a feature, not a bug. Subscribe for weekly takes on AI, startups, and building things that matter.