iOS app listed self-hosted workers as part of remote control option

[Calvin_Ng]

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

On web, remote control and self-hosted pool are setup as isolated options.

• Self hosted pool is launched explicitly through ‘agent start worker’
• Remote control is automatically turned on when IDE opened

I run a setup which I turned off remote control and only turned on self-hosted pool.

On web, Im still able to access my self hosted pool workers, but on iOS the self hosted pool workers is only available if i turn on remote control.

This is a regression.

Steps to Reproduce

• Open iOS app
• Tap on destination selector when creating a prompt
• Observe self-hosted pool workers can’t be selected unless remote control is turned on.

Expected Behavior

• Self hosted pool woker is available even remote control is disabled.

Screenshots / Screen Recordings

Operating System

Other

Version Information

Cursor for iOS: v1.5.0 (39006)

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the detailed report and screenshots. What you’re describing is really a mismatch between surfaces: on web self-hosted, workers are available with Remote Control turned off, but on iOS the picker requires it to be enabled. That shouldn’t happen, and it’s not anything in your setup. I’ve shared this with the team and we’re tracking it. I can’t give an ETA yet, but I’ll post an update here once I have one.

For now, the workaround is to enable Enable Remote Control in dashboard > Cloud Agents. The side effect you were avoiding, where the desktop auto-registers as a machine, only happens while the desktop IDE is open, so it shouldn’t affect the workers you explicitly started via agent worker start.

Let me know if that helps.