Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The October 6 announcement introduces mobile control. Use current mobile setup guidance rather than relying only on the older announcement.
- Current prerequisites include Cursor 3.9.8 or later, Cloud Agents access, allowed cloud storage, and team administrator enablement.
- Planning runs in Cursor's cloud while commands, edits, tests, and Git tools run locally. Offline computers cannot sustain local execution.
- Mobile supports conversation and results; terminal, file browsing, and some administration still need web or desktop.
Why the computer must stay on
Cursor introduced iOS viewing and continuation of local agents October 6, 2026. It suits tracking long tasks or adding instructions away from the desk, not moving the whole project to the phone.
Current guidance separates cloud planning/model conversation from local command execution, edits, tests, and Git. The phone controls; the computer still runs tools.
Keep the computer awake and connected. Cursor provides a plugged-in keep-awake setting; the October 6 post also recommends power and an open laptop lid. Leaving the desk does not mean local tasks continue through shutdown or sleep.
Version, account, and team settings
Desktop Cursor must be 3.9.8 or newer. Older versions lack Remote Control in Settings, Agents and /remote-control. Mobile requires iOS 26.0 or iPadOS 26.0, currently in English; Android is planned.
The account needs supported-plan Cloud Agents access and cloud data storage. Listed plans are Start, Pro, Pro+, Ultra, Teams, and Enterprise, without replacing actual account permissions or specifying a separate Remote Control charge.
Teams/Enterprise administrators must enable the related access in Dashboard, Cloud Agents, Self-Hosted. Current guidance says Remote Control also enables self-hosted worker access. A worker runs tools; teams should verify policy compatibility first.
The October 6 post said Cloud Agents were unnecessary, agents stayed in place, and access defaulted on except Enterprise. Current guidance separates cloud planning from local tools and requires the conditions above. This guide follows the current steps without guessing when the difference arose.
Connect the same desktop agent to your phone
Step 1: use the same Cursor account on desktop and mobile and keep the computer online. Remote Control currently supports Agents Window, enabled under its Settings, Agents; the ordinary editor entry is not equivalent.
Step 2: run /remote-control in the desired agent's composer, then send the next message. Current guidance hands the session to a local worker prepared automatically, without deploying another execution environment.
Step 3: find that agent in the mobile inbox, inspect status, continue messaging, and check results. Local directories and Remote SSH workspaces are supported without a Git remote; SSH still depends on an authorized working connection.
Hypothetical, unexecuted example: ask the desktop agent to organize a document, then add from mobile, list missing information first without editing files. On return, check responses and artifacts. A sent message is not a completed task.
Local files do not mean no cloud processing
Documentation says repositories, secrets, credentials, and build caches stay local, but tool results, conversation state, and model context go to Cursor. File location and processed data scope need separate checks.
Cloud data storage is required; organizations forbidding it cannot use this control. Only the owner controls their agent, with sessions bound to account and machine, but that does not replace organizational review of materials, outputs, and tool permissions.
Legacy privacy mode must migrate to Privacy Mode, and confirmation cannot be reversed to legacy. Read policies and prompts before deciding; this is not an easily reversible switch merely for a trial.
If access is missing, check in order
First verify desktop 3.9.8, Agents Window, and Remote Control under Settings, Agents. Solve version and entry-point issues before repeating commands from mobile.
Then verify matching accounts, Cloud Agents access, cloud-storage permission, and team Self-Hosted enablement. Permissions and disconnection can look similar; an absent inbox entry alone does not prove a network fault.
Finally check whether the next message was sent after /remote-control, the computer is awake and online, and workspace tools work. Keep exact prompts and states against official guidance. This guide paired no devices and verified no account.
What still needs web or desktop
Mobile suits progress, instructions, and results. Current guidance lists terminal/file browsing, billing/admin, source-control connections, environment secrets, and MCP management as web-side functions. Not every desktop management action is available on mobile.
Distinguish cloud agents, whose compute Cursor provides, from local control, which depends on your computer's tools. A sleeping phone and powered-off computer differ. Check the actual execution mode if work must continue while your computer is offline.
Sources
Frequently Asked Questions
Does a workspace need a Git remote?
No, current guidance supports local and Remote SSH workspaces without one. Tools, permissions, workspace, and authorized remote connections still need to work.
Does mobile automatically move interrupted local work to the cloud?
The guide gives no such automatic migration. Restore the computer's connection and inspect the same agent; an accessible conversation does not prove local tools continue.
Should I send SSH or proxy passwords to the agent?
Remote Control does not expand necessary credential access. Use authorized connections and minimum tools; do not paste passwords, keys, or private links for pairing or troubleshooting.