Cursor released its first iOS app at the end of June. I spent the launch week with it on my phone: on trains, between sessions, and anywhere I was away from my desk but still responsible for code moving forward.

This is not a desktop replacement. It is a control surface for work that already runs in Cursor.

What the app actually does

Cursor for iOS gives you two modes that matter:

  • Cloud agents you can launch from anywhere and let run while you are offline from your Mac.
  • Remote Control for agents already running on your computer, so the phone becomes a second screen for steering, not restarting.

On top of that, the app leans into what iOS is good at:

  • Live Activities and push notifications when an agent finishes or needs input.
  • Review on the go: screenshots, videos of changes, annotated feedback, diffs, and pull request merges from the phone.
  • Voice when typing on glass is the wrong interface.

If you ship software, the interesting shift is not "I coded an entire feature on iPhone." It is "I did not lose the thread because I left my desk."

Why I cared as an ambassador

I run adoption programs across Germany. Most developers still picture AI coding as something that happens in a dark room with an external monitor. Mobile breaks that picture in a useful way.

The people I meet at Café Cursor and Build Days do not need another demo of autocomplete. They need believable workflows they can repeat on Monday. Cursor for iOS is one of those workflows: kick off work before you sit down, review output on the way somewhere, unblock an agent when it stalls.

That is adoption you can feel, not slides about productivity.

What I tried in practice

During launch week I used the app the way I actually travel: train rides, short gaps between community work, evenings when opening a laptop felt heavier than it should.

A few patterns held up:

  • Start cloud work early. Queue the agent before transit, then use the ride to review instead of context-switch back to a Mac.
  • Treat the phone as review-first. The merge flow is real, but the win is catching mistakes before they land.
  • Let notifications do the scheduling. Live Activities beat refreshing a tab when an agent is running long.

Composer 2.5 was 75% off in the mobile app through July 5, which made it a good week to stress-test the workflow without treating every run like a billing experiment.

What is still desktop work

I would not pretend the phone replaces a full repo checkout, a test suite, or the judgment call at the end of a large refactor. Cursor says cloud agents will keep moving toward parity with local machines. Until then, Remote Control and handoffs between phone and Mac are the honest model.

That is fine. Most teams do not need infinite coding on a 6-inch screen. They need fewer dead zones in the day when engineering stops because the builder left the chair.

Try it

Download Cursor on the App Store. Read the launch thread on X. If you are in Germany and want to see how others are using it in the room, watch cursorgermany.com.