Cursor Mobile App Can Remotely Control Computer Proxies
On October 6, Cursor opened remote control: users can view and respond to local proxies running on their computers through the iOS app, and can also initiate new tasks from their phones. The official statement added that proxies running on the computer will continue even if the phone loses signal.
Connecting does not move tasks. The update log specifies that remote control does not change the location of the proxy; the app simply connects to it. The computer must be on and online. There is a setting in the desktop to "keep this computer awake," and it requires being plugged in with the lid open. Computers under the same account will automatically appear in the app, and pairing must be approved on the desktop after selection. Local proxies are listed, and users can see what they are doing or send them messages.
The default switch is separated by organization type. Remote control is enabled by default except for enterprise organizations, where administrators must enable it separately in the organization's security and identity settings. It can be used without relying on cloud proxies. The official documentation also outlines a handover path: after entering the remote control command, the session is handed over to the worker on the machine, and the phone continues to issue commands. Terminals, file modifications, and testing still occur on the computer, using the original local environment.
The mobile app has not just been available since this day. On June 29, the Cursor iOS public beta opened to all paid plans, allowing users to select repositories, choose cutting-edge models, use voice input, and start cloud proxies with slash commands. Cloud proxies run in isolated virtual machines. Local sessions can also be moved to the cloud first, and the laptop can be closed while continuing. Lock screen notifications provide real-time activity updates, pushing notifications when proxies complete tasks, require input, or can be reviewed. Users can view demos, screenshots, logs, and differences on their phones, leave further instructions, or directly merge pull requests.
October 6 added this local layer. Cloud proxies solve the issue of needing to run after the computer is turned off. Remote control addresses keeping code, keys, and testing environments on the user's machine, allowing users to check and respond using only their phones. Proxies initiated from the phone will be marked as coming from the iOS app.
This represents a shift in control, not a procurement of computing power. The tasks are still run on the user's own computer, with Cursor providing pairing and mobile access. The driving force is the need for proxies to run long tasks while users cannot sit at their desks continuously. Beneficiaries are paid users who want to step away but still wish to interject. The pressure is on enterprise administrators who must first conduct security approvals, as well as programming proxies that rely solely on cloud virtual machines. If the computer sleeps, this link is broken.
Source: Public Information
ABAB AI Insight
Cursor's development has progressed from autocomplete in the editor to cloud proxies, and now to mobile. The iOS public beta in June initially offered cloud virtual machines: repositories, models, and voice were remote, allowing the laptop to be closed. The October 6 update integrates local proxies into the same inbox, acknowledging that some tasks cannot leave the user's file system and testing environment. Cloud and local now coexist rather than replace each other.
No new hardware bills are incurred. What is being mobilized is session control. Pairing must be approved on the desktop, and enterprise organizations have it disabled by default, requiring administrators to enable it in security and identity settings. The motivation is to move the waiting time for long tasks away from the workstation while not forcing users to hand over repositories to cloud virtual machines. The requirements to keep awake, be plugged in, and have the lid open indicate that computing power remains tied to that computer.
In comparison, GitHub has moved the Copilot coding proxy to cloud pull requests, and OpenAI has placed Codex tasks in remote sandboxes. The difference is that Cursor now allows loops or commands to be handed over between the phone and worker, while tool calls remain on the local machine. The industry position is in a control period. Proxies can already modify code themselves, and the current contention is about who can interject midway after a person leaves.
Structurally, this represents a transfer of pricing power. What is scarce is no longer model calls, but the approval rights when tasks are halfway through. The mechanism is that the phone becomes a review terminal, while the computer becomes an execution terminal. Losing signal does not affect loops already on the computer, but computer sleep will cut off the entire remote control. The default closure for enterprises returns the switch for this link from individual users back to administrators.
ABAB News · Cognitive Laws
People can leave, but the execution environment cannot sleep.
The phone holds the right to interject, not computing power.
The default off setting is the true product for enterprises.