Code From Your Phone: Cursor iOS vs Kiro vs Codex

Your Phone Is a Supervision Surface

Here is the honest answer before the demos win you over: none of these apps turns your phone into a code editor. Cursor for iOS, Kiro for iOS, and Codex inside the ChatGPT app are supervision surfaces. You use them to launch a coding agent, steer it while it works, and approve or reject the diff it produces. The real compute runs somewhere else: a cloud VM, an AWS backend, or your own Mac at home. Your phone is the remote control, not the workstation.

Once you accept that framing, these apps get genuinely useful. They are good for kicking off work on your commute, checking on a long agent run, reviewing and merging a pull request from a coffee shop, or turning a screenshot of a broken screen into a task an agent picks up. They are not good for hand-editing files, deep interactive debugging, or anything that wants a real keyboard. If you expected a mobile VS Code, you will be disappointed. If you wanted a control plane for agents you already trust, this is the wave you were waiting for.

Cursor vs Kiro vs Codex

All three landed within about six weeks of each other, but they are built for different people. The sharpest splits are platform (Codex is the only one on Android), the plan you need, and where the code actually runs. One thing to flag up front: several outlets tied Cursor's iOS launch to a SpaceX acquisition of Anysphere, but there is no first-party confirmation, so this table marks it as reported and unverified.

The quick read: pick Codex if you are on Android or want zero cost to start with your own Mac doing the work; pick Cursor if you already live in Cursor and want the richest mobile client; request Kiro if your team is on AWS and wants spec-driven autonomy. The rest of this guide is the setup detail that the launch videos skip.

Setting Up Cursor for iOS

Install the app, open it, choose a repository, and launch an agent the same way you would on desktop. Cursor can run the agent as a cloud agent in an isolated VM or remote-control an agent on your Mac. For the desktop route, turn on Remote Control and the "keep computer awake" setting so the machine does not sleep mid-run.

The gotcha that cost people time at launch is that enabling agents takes two separate toggles, not one. As Hamel Husain put it, you enable cloud agents in the web dashboard, then go into Cursor's agents view and select "local & remote." Miss either and the phone shows nothing on the remote-control screen.

Once it works, the mobile client is the most feature-dense of the three: voice input, slash commands, any frontier model, push notifications, lock-screen Live Activities that show agent progress, and a local-to-cloud handoff so you can start on desktop and continue on the phone. You can review and merge pull requests without opening a laptop. Cursor pitches it for on-call incidents, reproducing customer bugs, and annotating a screenshot before handing it to an agent as visual context.

Two honest caveats. The remote-control and local-proxy path was buggy at launch, with users reporting empty remote-control screens even after enabling everything, and the rollout is US-first with no Android yet. Also time-sensitive: Cursor is running its Composer 2.5 model at 75% off in-app through July 5, 2026. If you plan to lean on it, that window is nearly closed as of this writing on July 1.

Setting Up Codex From Your Phone

Codex mobile does not have its own app. It lives inside the ChatGPT app, which is why it reaches iOS, iPad, and Android while the others are iOS-first. Setup is the simplest of the three: install Codex on your Mac, and the desktop app shows a QR code. Scan it from ChatGPT on your phone and the two link up. From there you can start work, review output, steer the agent, approve commands, and switch models across all your threads.

The security model is the selling point. In OpenAI's words, your code, credentials, and project context stay on your machine, and only real-time updates stream to the phone through a secure relay. The phone never holds the repo. That also sets the main limit: the desktop half is macOS only at launch, with Windows described as coming but without a date. One live reliability note worth keeping in mind: on June 29 and 30, 2026 the Codex team fought a usage-drain bug across CLI and desktop and reset limits, so mobile Codex stability is a topical question right now rather than a settled one.

Setting Up Kiro for iOS

Kiro is the most gated of the three. It is a preview you have to request access to, it is iOS only, and it requires iOS 26 or later. Access is limited to paid tiers: Pro, Pro+, Pro Max, or Power. Once you are in, you sign in and can kick off, monitor, steer, and interact with your Kiro sessions from the phone. AWS frames it plainly: check in while grabbing coffee, come back to a pull request.

What makes Kiro distinct is its three modes: chat for conversation, spec for spec-driven work, and autonomy for letting it run. The backend lives in the AWS cloud and keeps working after your screen turns off, which suits long autonomous jobs. It launched the same week as Kiro CLI 3.0, and Kiro itself arrived in May 2026 as the replacement for Amazon Q Developer. Like the others, it is a supervision surface, not a mobile editor.

The Antigravity Mobile Gap

If you use Google Antigravity, the obvious question is: where is ours? As of July 1, 2026 there is no first-party Antigravity mobile app. Antigravity ships a capable CLI with Goal Mode and subagents, but nothing that puts a supervision surface in your pocket the way Cursor, Kiro, and Codex now do.

The demand is explicit. On r/google_antigravity, a thread asking for "the equivalent of codex mobile app / claude code remote" captured the mood exactly: coding on mobile is a game changer, and users want to send files and steer runs the way they can on Codex or Claude Code. The only answer offered was a community workaround rather than an official app: a self-hosted web UI called claudecodeui that wraps a CLI agent in a browser you can open on your phone. If you are weighing platforms on more than mobile, see our Antigravity vs Claude Code comparison and our roundup of the best Antigravity alternatives in 2026.

Build Your Own: VPS + Tailscale

A vocal camp argues you do not need any of these apps. You need a VPS and a phone SSH client. The reference implementation making the rounds is pocketdev from Massi: a Hetzner box running your AI CLI of choice (Claude Code, Codex, Cursor, or Gemini) on your own subscription, reachable only over Tailscale, where pocketdev publish ships a live URL through a Cloudflare tunnel. As Denis Yurchak summarized the appeal: you do not pay anyone but Hetzner and a terminal app to code from your phone on your own VPS.

Others are packaging the same idea. OpenClaw shipped native iOS and Android apps for self-hosted, bring-your-own-key agents, with a tidy framing: your phone is not the assistant, it is a node. The through-line across the whole category is that the phone is becoming a control plane for agents, not a place where code gets typed. If you go the self-hosted route, wiring your CLI agent to real tools matters as much as the hosting, so it is worth reading our guide to the best MCP servers for Claude Code before you lock in a stack.

FAQ

Glossary

Which Should You Pick?

There is no single winner, because these tools answer different questions. Use Codex if you are on Android, want the cheapest path in, or like that your code never leaves your Mac. Use Cursor for iOS if you already pay for Cursor and want the most complete mobile client, and grab the Composer 2.5 discount before July 5 if you plan to use it. Request Kiro if your team is on AWS and wants spec-driven, autonomous runs that keep going after the screen sleeps. And if you are on Google Antigravity, there is no first-party app yet, so a self-hosted web UI like claudecodeui or a VPS-plus-Tailscale setup is the realistic answer today.

Whatever you choose, evaluate it as a supervision tool. The question is not whether you can type code on a 6-inch screen. It is whether you trust an agent enough to launch it, watch it, and approve its work while you are away from your desk. Where that trust exists, these apps genuinely extend your working day. Where it does not, no amount of mobile polish will help.

Sources

Claims above are grounded in the official launch pages and docs, first-party social posts, and clearly-labeled press and community context. The Cursor and SpaceX connection is reported by press outlets only and is unverified as of July 1, 2026.

Official docs and pages

• Cursor blog: Cursor for iOS
• Cursor on the App Store
• Cursor dashboard: enable cloud agents
• OpenAI: work with Codex from anywhere
• Kiro (AWS)

First-party social

• @cursor_ai: Introducing Cursor for iOS
• @kirodotdev: Kiro is now on iOS
• @OpenAI: Codex in the ChatGPT mobile app

Reported / press

• 9to5Mac: OpenAI brings Codex control to ChatGPT for iPhone and Android
• The New Stack: AWS Kiro mobile and agentic coding
• The Register: AWS puts Kiro in your pocket

Community and build-your-own

• @HamelHusain: enable Cursor agents in two places
• r/google_antigravity: requests for a mobile equivalent
• claudecodeui (community web UI for CLI agents)
• @0xMassi: pocketdev (Hetzner + Tailscale)