Hey, thanks for the report. Quick important note: Composer’s advice to disable Privacy Mode is wrong. Remote Control works with Privacy Mode in shared mode. It only gets disabled if you fully block cloud data storage, so that’s not the reason.
Your version 3.9.16 and plan Pro are supported, so it’s not that either. Let’s go step by step:
- Remote Control is enabled on desktop, not in the iOS app. On Mac: Settings > Agents, then turn on Remote Control. Or in the agent input run
/remote-controland send the next message, the session will be handed off to the worker on your machine. - Your Mac must stay online and logged in. You can enable Keep this computer awake.
- After that, the session should show up in the iOS app inbox under the same account.
The key requirement that often breaks this: the workspace must be Git-backed, and its remote must be resolvable by Cursor Cloud. If your repo is on a self-hosted Git server like your own GitLab or GitHub Enterprise, Cursor Cloud can’t see it unless that instance is configured separately, and then the session won’t surface on your phone.
To confirm the self-hosted case: what host is your repo on? As a quick test, try Remote Control in a project whose remote is on github.com or gitlab.com. If it works there, the blocker is the self-hosted repo resolution.
Helpful links:
Let me know what you see with the cloud-hosted repo test.