Cursor for iOS displays fewer Remote Controls than expected.
It appears to show only one Remote Control per computer, even when multiple Agent Workers are running on the same computer.
The web version of Cursor Cloud Agent displays the correct number of Remote Controls on both desktop and mobile browsers. The Remote Controls missing from the iOS app are active and work correctly when selected from the web version.
Steps to Reproduce
Open multiple repositories in separate tabs.
Start an Agent Worker in each repository.
Run multiple Agent Workers on the same physical computer.
In my case, I use Windows Subsystem for Linux and have three different WSL distributions running.
Open the Remote Control list in Cursor for iOS.
Compare the list with the Remote Control list in the web version of Cursor Cloud Agent.
Cursor for iOS shows only a subset of the active Remote Controls, while the web version shows all of them.
Expected Behavior
Cursor for iOS should display all active Remote Controls, matching the Remote Controls shown in the web version.
All displayed Remote Controls should be selectable and usable.
On iOS the Remote Control list is grouped per computer (one row per machine), while the web version lists one row per worker. So when several agent workers run on the same physical machine (like your three WSL distros on one Windows host), iOS collapses them into a single Remote Control entry while the web shows each one separately. That’s why the counts differ.
The good news is the “missing” workers are usually still reachable from iOS. Since each of your workers is tied to a different repository, select the machine under Remote Control in the Runtime picker, then set the composer’s repository/target to the specific repo you want. iOS routes to the matching worker on that machine based on the repo you’ve targeted.
The one exception is two workers on the same machine serving the same repository, where only one is currently selectable on iOS. For that case the web version (which also works in mobile browsers) reaches every worker individually.
I’ve reported the per-machine vs per-worker difference to our team so the iOS list can better match the web. I’ll follow up here as there’s progress.
The team looked at the per-machine vs per-worker difference, and for now the iOS Remote Control list will stay grouped by computer (one row per machine). It’s an intentional design choice rather than a bug, so the counts will continue to differ from the web version.
Selecting the machine and setting the composer’s repository to the one you want still routes to the matching worker on iOS, and the web version remains the way to reach a specific worker when several share the same repository on a single machine.
