Blocked: I’m unable to create new automations that run on self-hosted workers.
I’m able to start a new agent session with my self-hosted worker, but that same worker is not available in the Automations UI as a runtime target. When clicking the dropdown, my only option is Cursor Cloud. When I save this automation, and try a test run, I can confirm the automation runs on Cursor Cloud environment and not my agent.
Steps to Reproduce
Create self-hosted agent.
Create Automation.
Runtime → Choose where runtime runs. Default: Cloud Agent
Clicking the drop down, can’t see or select my self-hosted agent. Only the default.
Expected Behavior
I believe I should be able to target my own self-hosted worker(?) I have a handful of other automations that all still target their self-hosted workers, and work just fine. Maybe I hit a limit, or this has been deprecated?
Hey, thanks for the detailed report. This makes things clear.
It looks like in the Automations creation UI, the self-hosted runtime option is gated by a team-level setting. So for accounts without a team, the dropdown only shows Cursor Cloud. At the same time, the worker in My Machines is picked up correctly in regular agent sessions, and existing automations keep working because the backend honors the saved privateWorker config regardless of what the UI shows. So this looks like a gap for individual Pro+ users, not a runtime bug.
To confirm and report this internally in a clean way, can you clarify a couple things:
Were the existing working automations created on this same individual Pro+ account that never had a team, or were they created via the API/SDK?
Can you share a screenshot of the Runtime dropdown in a new Automation, expanded, so we can capture exactly what you’re seeing?
In the meantime, as a workaround: creating or updating an Automation via the API with an explicit privateWorker config should work, since the backend accepts it. If you need to unblock right now and want the exact request format, tell me and we’ll share it.
I can’t give an ETA for the UI fix yet, but I’ll file the report. We’ll post updates here if I get any.
The existing working automations were created manually on this same individual account, that never had a team. This account was recently upgraded to Pro+ from Pro. Previous automations were made under “Pro”.
Included the screenshot of the new automation only showing Cursor Cloud.
Thanks, that completes the picture. Confirming what I’m seeing:
In the new Automation Runtime dropdown, it only shows Cursor Cloud. Your worker nightly-securit... only appears in the dropdown for existing automations because the backend stores and applies their privateWorker config.
In the current Automations UI, the self-hosted runtime option is gated by a team-level setting. For individual accounts without a team, this flag is always false, so new automations can’t select your worker. The fact that this used to work on Pro is part of the gap you’ve run into.
I’ve reported this internally as a gap for the individual Pro+ flow. I can’t share an ETA, but we’ll post an update in the thread as soon as we have one.
