Skip to content
NewsProduct launch

Cursor's iOS app can now watch and reply to agents that never leave your desktop

· by Pondero Newsdesk

The short version

Cursor shipped a version of Remote Control that keeps the coding agent fully on a developer's own machine while the iOS app connects in, a different architecture from the cloud-routed Remote Control it shipped in July.

Cursor's iOS app can now watch and reply to agents that never leave your desktop

A developer can now check on and reply to a Cursor agent from an iPhone while the agent, and the code it is touching, stays entirely on the developer's own computer, rather than handing the task to Cursor's cloud, per Cursor's changelog entry, "Remote control for local agents," published October 6.

What changed

"You can now see and reply to the local agents running on your computer from the Cursor iOS app," Cursor wrote in the entry. That is a different setup than the Remote Control feature Cursor shipped in July, where "the agent loop moves to the cloud while its tools keep running on your machine," according to a breakdown from Product Compass. Checking in from a phone on the July version meant Cursor's servers took over running the agent's reasoning step; the new version, per Cursor's own changelog, "doesn't move your agents anywhere. It keeps running on your computer, and the app connects to it."

Setup is a download-and-pair flow: install the iOS app, sign in, and approve a pairing request from the desktop to link the two. From there, a developer can view an agent's output or send it a reply from their phone while it keeps executing on the desktop machine, per the changelog.

Enterprise teams get an opt-in switch, not the default

Remote Control is on by default for everyone, Cursor said in the changelog, except Enterprise organizations, where it ships off and an admin has to turn it on under Org settings, Security and identity, Remote control. The local-agent pitch is that code and agent reasoning never leave the machine where they started, which is exactly the claim a security team would want to verify before approving it. Cursor also flagged the practical catch: "your computer needs to stay on and online for remote control to work," and it ships a "Keep this computer awake" toggle that requires the laptop to stay plugged in with the lid open.

That tradeoff gives developers a choice between two architectures rather than one upgraded feature. Pick the local version when the code cannot leave the machine and someone can leave a plugged-in, lid-open laptop running; pick the July cloud-routed version when the laptop might be off and the agent's tool access can tolerate running through Cursor's servers instead.

What to watch next

Cursor has not said whether Remote Control reaches Android, and the changelog is silent on push notifications for when an agent finishes or needs approval, something that would make checking in from a phone less dependent on opening the app. Whether more Enterprise admins flip the setting on, now that the agent itself never has to touch Cursor's cloud, is also worth tracking as a signal of how security teams weigh the two architectures.

Sources