# Cursor lets you reply to local agents from an iPhone, while the work stays on your computer

> Remote Control connects the iOS app to an agent running on your desktop. The computer still needs to remain on and online; this does not move the job to the cloud.

Canonical: https://stacktak.com/news/cursor-remote-control-local-agents-ios
Author: Stacktak Editorial
Published: 2026-10-07T14:00:00.000Z
Modified: 2026-10-20T19:30:27Z

An agent waiting for a clarification can stall a task while you are away from your desk. Cursor’s October 6 Remote Control update lets users see and reply to local agents through its iOS app.

The setup pairs a computer on the same account with the phone, with approval in the desktop application. Cursor says the agent continues running on that computer, which must stay powered on and connected. Remote Control does not require cloud agents. Enterprise organizations have a separate administrator setting to enable the feature. [The changelog](https://cursor.com/changelog/remote-control-local-agents) describes those conditions.

## A remote conversation, with local dependencies

The distinction matters for a developer who starts a task and then closes a laptop. A phone connection is not an independent execution environment; the desktop remains part of the workflow. Availability depends on that machine continuing to run.

For a first trial, use a small task with an obvious stopping point. Verify that the phone displays the expected session and that a reply reaches the right agent. A short message can help unblock work, but inspecting a substantial code change still calls for the repository, the tests, and enough screen space to review it carefully.

## Source

[Cursor — Remote control for local agents, October 6](https://cursor.com/changelog/remote-control-local-agents).