Cursor Remote Control: Steer Local Agents From Your iPhone
Cursor now lets you watch and reply to agents running on your own computer from its iOS app. Here is what the 06/10/2026 release changes for UK teams and the settings to check first.
Cursor has made it possible to keep an eye on a coding agent without sitting at your desk.
What happened
On 06/10/2026 Cursor released remote control for local agents.
You can now see and reply to the agents running on your computer from the Cursor iOS app.
Remote control is on by default for everyone except Enterprise organisations.
Setup is short.
You download the Cursor iOS app and sign in, and the computers on your account appear automatically.
You tap your computer in the app, then approve the pairing request in the Cursor desktop app.
Your local agents then appear in a list, and tapping one shows what it is doing or lets you send it a message.
The agents do not move anywhere.
They keep running on your computer, and the phone app simply connects to them.
That means your computer has to stay on and online for remote control to work.
Cursor has added a setting called Keep this computer awake, under Remote Control in the desktop settings, to stop the machine sleeping while you are away.
For that setting to work, the computer needs to be plugged in with the lid open.
Enterprise admins can switch the feature on in Org settings, under Security and identity, then Remote control.
Cursor also says remote control does not require cloud agents.
Why this matters for UK businesses
If your team runs Cursor agents on a developer laptop rather than in the cloud, this release is aimed squarely at you.
Until now, a long agent run on a laptop meant someone had to be at that laptop to answer a question or correct a wrong turn.
An agent sitting idle while it waits for a reply is lost time, and on a busy client day that quietly eats into delivery.
Remote control lets a developer check progress and unblock the agent from a phone between meetings, on the train, or at a client site.
Because the agent still runs on the local machine, the code, build outputs and local secrets stay where they already are.
That is a different trade off from cloud agents, where the work runs on a computer in the cloud.
For firms with strict client confidentiality terms, keeping execution on a known machine may be easier to approve than moving work to a hosted environment.
There is a governance point too.
Because the feature is on by default for every plan except Enterprise, a business on a smaller Cursor plan may already have it switched on without anyone deciding to.
A phone that can message an agent with access to your codebase is now part of your security perimeter.
If staff use personal iPhones for work, that question belongs in your device policy rather than being left to chance.
Enterprise organisations get the opposite default, so an admin has to make a deliberate choice before anyone can use it.
The Keep this computer awake option also has a practical cost.
A laptop left plugged in, open and awake in an empty office or at home overnight is a physical security and energy question, so decide where those machines live.
How we see it at Adevious AI
We would treat remote control as a useful convenience, not a reason to leave agents running unattended for days.
First, decide whether you want the feature on at all, and write that down as a team rule.
Second, if you allow it, limit it to company managed iPhones with a screen lock.
Make sure staff only approve pairing requests in the desktop app that they started themselves.
Third, when nobody is at the desk, keep agents on lower risk work such as tests, refactors and documentation.
Fourth, pick one or two machines that can stay plugged in and awake, rather than every laptop in the business.
The release names only the iOS app, so it does not help Android users today.
The bigger picture
This release fills a gap between Cursor's local and cloud options.
In September Cursor launched Projects, which run on a cloud computer so closing your laptop does not stop them.
It also added self hosted machines, which keep tool execution inside your own network.
Remote control gives the plain local setup some of that freedom, without moving the work off your own hardware.
For most UK teams, the sensible next step is a short trial on one machine and one phone.
Follow that with a clear decision on who is allowed to use it and for which kinds of work.
Sources
Cursor, Changelog, Remote control for local agents, 06/10/2026: https://cursor.com/changelog
Cursor, Blog and changelog index: https://cursor.com/blog
Acronyms
AI: Artificial Intelligence
iOS: iPhone Operating System
UK: United Kingdom