Update (2026-10-07): I rechecked Cursor's changelog and mobile documentation; the two pages still describe different execution models.
Cursor Remote Control has two incompatible official descriptions. The changelog dated 2026-10-06 says the agent keeps running on the user's computer and that Cloud Agents are not required. Cursor's mobile docs say the agent loop moves to Cursor's cloud while terminal commands, file edits, tests, and git run on the computer. As of 2026-10-07, the pages disagree about where the loop runs.
Key facts
- Cursor's changelog dated 2026-10-06 describes Remote Control in the Cursor iOS app.
- The changelog says Remote Control is on by default except for Enterprise organizations, and says it does not require Cloud Agents.
- The mobile documentation requires Cursor client version 3.9.8 or later and a supported account with Cloud Agents access.
- The mobile documentation says the agent loop runs in Cursor's cloud while terminal commands, file edits, tests, and git run on the local computer.
- The changelog describes pairing by selecting a computer in the iOS app and approving the request in the desktop app. The docs describe running
/remote-controlin the desktop agent input. - Both pages require the computer to stay on and online. Cursor's settings include “Keep this computer awake”; the changelog also specifies power and an open lid.
How does Cursor Remote Control pair a phone with a desktop?
The changelog's pairing flow is account-based: sign in to the iOS app, select a computer shown for the account, approve the pairing request in Cursor's desktop app, and then select a local agent to inspect or message. The page presents this as the path for the feature announced on 2026-10-06.
The mobile documentation describes a different handoff. On Cursor 3.9.8 or later, enable Remote Control under Settings > Agents, run /remote-control in the agent's input on the computer, and send the next message. The session then appears in the mobile inbox. The two descriptions may reflect two entry points, but neither page explains how they relate.
The phone is a control surface, not a replacement for the desktop workspace. That is distinct from Cursor SDK can steer an agent mid-run, which describes an SDK call, and from the delegation patterns in Five ways a lead agent runs a crew. Remote Control's shared requirement is that the computer remains available for the work.
Why do Cursor's changelog and mobile docs disagree?
The changelog gives a local-loop description: “Remote control doesn't move your agents anywhere.” It also says that Remote Control “doesn't require cloud agents to work.” Those sentences describe the iOS app as a connection to an agent that continues on the computer. (Cursor changelog, 2026-10-06)
The mobile documentation gives a split description: “The agent loop moves to the cloud while its tools keep running on your machine.” Its detailed section names terminal commands, file edits, tests, and git as local tool calls, and says that conversation state and the model context needed to continue cross to Cursor. (Cursor mobile docs)
The practical overlap is clear even though the loop location is not. The computer still needs the repository, local setup, and an awake network connection because the tool calls cannot run while it is asleep or offline. The unresolved question is whether the changelog describes a separate local-session mode or whether one of the official pages is stale.
What does Cursor Remote Control require on 2026-10-07?
The documented handoff requires Cursor 3.9.8 or later, a supported account with Cloud Agents access, an enabled Remote Control setting, permission for cloud data storage, and an awake computer with network access.
- Client: Cursor 3.9.8 or later is required; older clients do not show the Remote Control setting or
/remote-controlcommand. - Plans: The docs list Start, Pro, Pro+, Ultra, Teams, and Enterprise accounts with Cloud Agents access.
- Workspace: Local and Remote SSH workspaces are supported, and the project does not need a Git remote.
- Machine: The computer must stay awake and online. Cursor documents Keep this computer awake under Settings > Agents and says the machine must be plugged in with the lid open.
- Teams and Enterprise: The docs put the administrator switch at Cursor Dashboard → Cloud Agents → Self-Hosted. The changelog names Org settings > Security and identity > Remote control for Enterprise organizations.
- Privacy: The mobile docs say Remote Control is unavailable when privacy settings disable cloud data storage.
Which execution model should a team rely on?
For an operating checklist, rely on the shared constraint: tool calls happen on the computer, so keep it awake, powered, and online. Treat the agent-loop location, Cloud Agents dependency, and activation flow as an unresolved documentation conflict until Cursor publishes a clarification.
Specification | Changelog dated 2026-10-06 | Mobile documentation read 2026-10-07 | Safe conclusion |
|---|---|---|---|
Agent loop | Stays on the computer | Moves to Cursor's cloud | Official pages conflict |
Tool execution | Local computer | Local computer | Keep the computer available |
Cloud Agents | Not required | Access is required for the documented handoff | Verify the account and mode |
Activation | Select a computer, then approve desktop pairing | Run | Follow the path shown by the installed client |
Team control | Enterprise exception under Org settings | Teams and Enterprise switch under Dashboard → Cloud Agents → Self-Hosted | Ask the admin which control is authoritative |
Sources
- Remote control for local agents · Cursor Changelog (read 2026-10-07)
- Cursor for iOS · Cursor Docs (read 2026-10-07)
- Cursor · Mobile Product Page (read 2026-10-07)
- Cursor SDK can steer an agent mid-run (read 2026-10-07)
- Five ways a lead agent runs a crew (read 2026-10-07)
Last verified: 2026-10-07.