User cloud instances on iOS / iPad application confusion

By default it seems the iOS/iPad application can use Cloud instances and Remote control. What it cannot do is run tasks on a user’s existing self hosted instances?

After some messing around it seems like newly registered instances now appear under Remote Control? This is a little confusing with two types of self hosted boxes and the old pool instances appearing in the user settings

If it helps, what I’d like to do is to drive a headless server from mobile, which was possible from the old web agent dashboard. It seems possible, but rather convoluted unless my old agent runner was causing issues

Or have I got all of this wrong? :melting_face: Could be worth a documentation update

Hey there!

Remote Control on iOS is the renamed My Machines list. A worker started with agent worker start without --pool registers as a personal, user-scoped machine, so your headless server lands there exactly like a laptop running Cursor would. To run a task on it, open the runtime picker in the composer and pick the machine under Remote Control. It needs Remote Control enabled both for your team and for you personally, and it won’t appear under Legacy Privacy Mode.

Your self-hosted pool is a separate section called Team Pools, and it only appears once at least one pool worker is registered. If none are, the section hides itself, which is likely why the pool looks like it disappeared. Pool workers use a different command and a different credential:

cd /path/to/repo
agent worker --pool start

That one needs a service account API key (export CURSOR_API_KEY="..."), not your personal user key. Personal keys only start My Machines workers, and service account keys only start pool workers. The pool is also an Enterprise feature gated by an admin toggle in Cloud Agents settings, so if your team’s plan or those settings changed, the section can go away for that reason too.

So the two kinds of self-hosted boxes are personal machines versus a shared team pool. The naming isn’t consistent across surfaces yet: mobile and the agent picker on the web both say “Remote Control”, while the dashboard settings page still says “My Machines” for the same list. That’s being cleaned up.

Your docs point is fair. The My Machines guide sends you to cursor.com/agents and never mentions those machines show up as “Remote Control” on iOS. We’ve let the team know. In the meantime, Choose where Cloud Agents run is the clearest side-by-side of the two, and Self-Hosted Pool has the full setup.

If Team Pools still doesn’t show up after registering a pool worker, let me know.