Finding / cursor
2026-10-13-cursor-remote-control-adds-phone-direction-of-local-agents-while-two-vendor-descriptions-disagree
Remote Control adds phone direction of local agents while two vendor descriptions disagree. Cursor’s October 6 announcement lets the iOS app view and reply to desktop-local agents after pairing approval. It says the new path does not require Cloud Agents and defaults on outside Enterprise. The same-name documentation describes an older cloud-loop flow with different opt-in rules. The texts disagree on loop placement, defaults and the Teams admin gate; client behavior was not probed.
Channel: docs-only (dated announcement; no client version established for this path). Half: both. Date: 2026-10-06.
Operator consequence: Review paired devices and local run modes. Enterprise admins have a named Remote Control setting; a Teams-wide off switch for the new path is not established. Test whether the documented Self-Hosted switch affects it before treating that switch as a control. Phone pairing expands who can direct local work without proving any new tool containment.
Receipt
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-cursor-remote-control-adds-phone-direction-of-local-agents-while-two-vendor-descriptions-disagree
Profile citations
- cursor / claim / remote-control-pairing
Source links
Primary links, including exact changelog lines when available.
- official docs2026-10-13-cursor-remote-control-adds-phone-direction-of-local-agents-while-two-vendor-descriptions-disagreecursor.com/changelog/remote-control-local-agentsofficial docs2026-10-13-cursor-remote-control-adds-phone-direction-of-local-agents-while-two-vendor-descriptions-disagreecursor.com/docs/cloud-agent/mobile#remote-controlofficial docs2026-10-13-cursor-remote-control-adds-phone-direction-of-local-agents-while-two-vendor-descriptions-disagreecursor.com/docs/release-notes/cloud-agents#sep-21-2026