Cursor Adds iOS Remote Control for Coding Agents Running on a Computer
Remote Control connects the mobile app to an existing computer rather than moving agent work to the cloud. Enterprise access requires an administrator’s approval.
Listen to this story
The audio brief
Story brief
3 key pointsCursor released Remote Control on October 6, 2026, adding a mobile way to monitor and message coding agents running on a developer’s desktop. It changes where developers can interact, not where work executes: the computer must stay on and online, and the feature does not require cloud agents. Enterprise organizations have Remote Control disabled by default, so an administrator must enable it before users can pair and approve access on a computer.
- 01
Users select a computer shown in the iOS app, approve pairing on that desktop, then choose an agent to view or message.
- 02
Cursor’s Keep this computer awake setting is intended for use while away, but requires the computer to be plugged in with its lid open.
- 03
Enterprise access requires both an organization-level setting in Security and identity and approval during desktop pairing.
Developers can now check a coding agent’s progress and send it instructions from Cursor’s iOS app without returning to their computer. Cursor released Remote Control on October 6, 2026. The phone provides access to agents running on the desktop; the computer still does the work and must remain on and online.
Pair on the desktop, then reply from the phone
- Download the Cursor iOS app and sign in. The app automatically shows computers on your account, providing the starting point for choosing which machine to connect to.
- Tap the computer in the mobile app, then approve its pairing request in Cursor on the desktop.
- Choose an agent from the list that appears after pairing. Tap it to see what it is doing or send a message; those are the controls Cursor describes for the mobile connection.
The computer remains the working machine
Remote Control changes where a developer can interact with an agent, not where that agent runs. The mobile app connects to the computer, and the agent stays there. Cursor says the feature does not require cloud agents, so using the mobile controls does not require switching the task to that separate form of execution.
Keeping that connection available takes some preparation before leaving the desk. Cursor offers a Keep this computer awake option under Remote Control in its desktop settings. It is intended to stop the machine from sleeping while the user is away. Cursor specifies that the computer needs to be plugged in with the lid open for this setting.
Enterprise teams have a separate access switch
For an Enterprise user, that organization-level setting and the desktop pairing approval are separate parts of getting connected. The administrator enables the feature for the organization; the pairing workflow then asks for approval on the selected computer.
Sources
- cursor.comRemote control for local agents · Cursor
Reader comments
Newest comments first. Replies stay oldest first.