Cursor Remote Control: Drive Agents From Your Phone

Remote Control is the official name in Cursor's docs for driving a local agent, one executing on your own machine, from your phone. It is the part of Cursor's mobile story that goes beyond cloud agents: the iOS launch post pitches launching always-on agents in the cloud, or "control agents running on your computer from your phone." Cloud agents run on Cursor's machines and never needed your desktop; Remote Control is specifically about the machine on your desk.

That distinction matters because local agents are where much real work happens: your checkouts, your environment, your build caches. Remote Control means stepping away from the desk no longer means abandoning a run in progress.

The architecture is one backend, three windows onto it. An agent started on any surface shows up on the others, which is what makes handoff feel like continuing rather than reconnecting. Each surface has a distinct job.

Cursor documents the requirements precisely, and each one follows from the same fact: the tool calls execute on your machine, not in the cloud. The phone is a steering wheel, not the engine.

The workflow that makes Remote Control click is the handoff: begin a run where the context is richest, your desktop, then carry supervision in your pocket. Here is the sequence end to end.

1. 1Start the run at your desk: kick off a local agent in the desktop Agents window, or a cloud agent from any surface.
2. 2Enable Remote Control in the Agents Window settings, and leave the machine awake and online.
3. 3Open Cursor for iOS. The same run is already listed, because the app reads the same backend.
4. 4Supervise from the phone: follow the log, answer the agent's questions, redirect with typed or dictated follow-ups.
5. 5Review the result in the app: full diffs, commits, deployments and review threads all render on the phone.
6. 6Close it out: merge with squash, toggle auto-merge, update the branch, or leave it for a desktop-grade review in the morning.

Mechanically, yes: a merge from the iOS app goes through the same pull request as a merge from anywhere else. Branch protections, required checks and code-owner rules still gate it. The app gives you the controls (merge with squash, mark ready for review, update the branch, toggle auto-merge, publish, close) and no bypass around your repo's rules.

The judgment question is different from the mechanical one. A phone screen shows you a diff; it does not give you the desktop's room to read surrounding code, run the change, or think. A policy that works in practice: supervise, comment and redirect freely from the phone, merge the small low-risk changes, and hold anything touching auth, payments, data migrations or infrastructure for a desktop review. Write down which actions your team treats as phone-safe, so the boundary is a decision rather than a mood.