Cursor Adds iOS Remote Control for Local Coding Agents
Developers can inspect and reply to agents away from the desktop, while execution stays on the host computer and enterprise access remains admin-controlled.
Edited by Tyronne Panaino
Cursor announced Remote Control for local agents on October 6, 2026, adding a way to view and reply to agents running on a computer from the Cursor iOS app. The change matters to developers supervising longer coding tasks because it extends oversight beyond the desktop without transferring the work to a separate cloud-agent environment.
The official Cursor changelog says computers associated with an account appear in the mobile app, but the user must approve a pairing request in the desktop application. Once paired, the iOS interface shows local agents and lets the user inspect their activity or send a response.
Mobile access does not move execution
Cursor draws a clear boundary around where the agent runs. Remote Control connects to an agent that remains active on the user's computer; it does not relocate the agent or its execution environment to Cursor's cloud-agent service. Cursor also says the feature works without cloud agents.
That design makes the host computer part of the operational path. Cursor says the machine must remain powered on and online for the mobile connection to work. The company points users to a desktop setting that keeps the computer awake, while noting that the machine must be plugged in with its lid open. In practice, the mobile app is a supervision surface, not a substitute runtime for an unavailable laptop or workstation.
Pairing and enterprise defaults shape access
The desktop approval step gives the person at the host machine an explicit pairing checkpoint before mobile control begins. Cursor says Remote Control is enabled by default for non-enterprise users. Enterprise organizations start with it disabled, and administrators can enable it through the Remote control area under Security and identity settings.
Those defaults are important for managed environments because the launch changes where agent sessions can be observed and answered. The announcement establishes the account, pairing and administrative controls, but it does not describe session encryption, device revocation, audit-log coverage, data retention, mobile-device-management integration or network architecture. Teams evaluating the feature still need those details from their own Cursor configuration and security review.
What changes for agent supervision
The immediate product delta is continuity of attention. A developer can leave the primary computer while keeping visibility into an agent that is already running, then answer it from the iOS app when the task needs input. The computer still supplies the execution environment, so local tools, files and processes remain tied to that host rather than being recreated on a remote service.
Cursor says the feature is available now in its iOS app. The changelog does not announce Android availability, service-level commitments, offline operation or independent security testing. Those omissions limit what can be concluded from the launch: the source confirms a new mobile control path and its stated operating conditions, not the security or reliability of every deployment.
Status
Confirmed. Cursor's official changelog documents the October 6 release, the iOS pairing flow, local execution boundary, host requirements and enterprise default. Internal confidence is medium because the evidence is a single first-party product announcement without independent operational or security verification.
Sources
Update note: Last reviewed 2026-10-11. We will revise this post if Cursor publishes additional platform, security or administration details.
Sources
- Cursor — Remote control for local agents — official
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.