Remote control for local agents
Remote control for local agents
Cursor iOS app now supports viewing and responding to local agents running on the user's computer, default enabled (excluding enterprise organizations). After downloading the app and logging in, the user's computer account is automatically displayed. Remote management requires pairing and authorization via the desktop app. Remote control only connects to the agent, does not move its running location, and requires the computer to be powered on and connected to the network.
You can now see and reply to the local agents running on your computer from the Cursor iOS app.
Get started
Remote Control is on by default for everyone except Enterprise organizations.
Download the Cursor iOS app and sign in. Computers on your account appear in the app automatically. Tap your computer in the app and approve your pairing request in the Cursor desktop app. Your local agents appear in a list. Tap one to see what it's doing or send it a message.
<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/remote-control-cl-pezewO3SZRrIQxMNaTzdpsP9TD1ChS.png" loading="lazy" alt="Remote Control for local agents in the Cursor iOS app" /><figcaption>Remote Control for local agents in the Cursor iOS app</figcaption></figure>
Agents keep running on your computer
Remote control doesn't move your agents anywhere. It keeps running on your computer, and the app connects to it. Your computer needs to stay on and online for remote control to work.
Keep your computer awake
To stop your computer from sleeping while you're away, turn on "Keep this computer awake" under Remote Control in Cursor's desktop settings. Your computer needs to be plugged in with the lid open.
For Enterprise teams
Remote control is on by default, except for Enterprise organizations. Enterprise admins can turn it on in Org settings > Security and identity > Remote control.
Remote control doesn't require cloud agents to work.
Remote control is available today in the Cursor iOS app.
Source: Cursor Changelog · cursor.com