Goal We need all Cursor Cloud Agent workloads for our team to run only on our self-hosted worker (machines in our account that connect outbound to Cursor). We must not use Cursor’s hosted cloud agent VMs for these runs. This applies to: Cursor Automations (e.g. Slack-triggered workflows) Programm…

Hi @Prashant_Varshney , The key setting you need is “Require Self-hosted Agents for All Cloud Agents.” It’s in your team dashboard at cursor.com/dashboard under the Cloud Agents tab, inside the Self-hosted Agents section. When enabled, all cloud agent runs for your team are forced to your self-hoste…

@mohitjain Can you help me? I try to enable the “Require Self-Hosted Pool for All Cloud Agents” option, but it automatically turns off.

This is a known bug on our side – the “Require Self-Hosted Pool for All Cloud Agents” toggle is failing to save for some teams. Our team is actively working on a fix. In the meantime, you can still route individual runs to your self-hosted workers: API (POST /v0/agents): Pass "usePrivateWorker":…

@mohitjain Any updates on this one?

Hi Daniel, Unfortunately, no update yet. We haven’t seen many reports of this, so the fix is still in progress on our end. I’ll follow up here as soon as it ships.

Any updates? @mohitjain 1 month has passed.

The fix is still in progress on our end. I understand this has been a long wait. In the meantime, the per-request workarounds I mentioned earlier should still work. I’ll follow up as soon as the fix ships.

Hey @Daniel_Weil ! [image] Daniel Weil: I try to enable the “Require Self-Hosted Pool for All Cloud Agents” option, but it automatically turns off. This should be fixed now. Sorry for the long wait, and let me know if you still hit any trouble!

How to ensure Automations and API agent runs use self-hosted workers only (not Cursor-hosted)?

Support Help

Daniel_Weil (Daniel Weil) April 10, 2026, 2:36pm 9

I don’t know if it is related, but when I try to create a self hosted Automation, I can’t choose the branch the repo should run on. So it results in error. I opened an issue here: Self Hosted Automations - Support / Bug Reports - Cursor - Community Forum

Topic		Replies	Views
Vulnerability Scanner agent — Environment selection silently reverts to "Cloud" after saving a self-hosted Pool Bug Reports cloud-agents	10	119	May 26, 2026
New automations aren't resolving self-hosted workers Bug Reports cloud-agents , automations	8	246	June 25, 2026
Can't change Cloud Agents team settings — backend rejects own stored no-ZDR consent ("noZdrModelConsents cannot be set via updateTeamAdminSettings") Bug Reports privacy-mode , teams-enterprise , cloud-agents	3	85	August 27, 2026
Self Hosted Automations Bug Reports cloud-agents , gitlab , automations	6	204	May 13, 2026
Launch new thread on "My Machines" in Cursor 3 IDE Feature Requests devcontainers , cloud-agents , agents-window	8	161	June 26, 2026

How to ensure Automations and API agent runs use self-hosted workers only (not Cursor-hosted)?

Related topics