When calling @cursor from slack, how to I instruct it to use my self hosted agent instead of cloud? I know I can do it from the web dashboard, but via slack it always spins a cloud vm instaed of using my personal environment.
Hey, thanks for the question.
Right now, the default Slack integration spins up a cloud VM. Support for self-hosted workers via Slack is something the team is working on, but it’s not fully implemented yet.
What you can try now:
- Make sure self-hosted agents are enabled in the Cloud Agents dashboard https://cursor.com/dashboard/cloud-agents#self-hosted-agents and that your worker is online.
- Try adding
@cursorin Slack withself_hosted=trueorprivate_worker=truein your message. There’s experimental support for this, but it can be unstable. - If you can, enable Use self-hosted workers globally in the Cloud Agents dashboard settings for all requests.
The team is aware of this limitation, and this is actively being worked on. There’s no exact ETA yet, but your request helps with prioritization.
Let me know if any of this works.
@deanrie hey, I got the same issue; It doesn’t work…
Hey, from the screenshots it looks like the pool is enabled and the worker is connected, so the issue is with the flag itself.
Right now the Slack integration only recognizes private_worker=true. The self_hosted=true syntax isn’t supported yet (they plan to add it as an alias, but it’s not released, and I can’t share a timeline).
Try one of these:
- In your message to
@Cursor, useprivate_worker=trueinstead ofself_hosted=true. - Or enable it globally in the Cloud Agents dashboard: https://cursor.com/dashboard/cloud-agents#self-hosted-agents. Then all Slack triggers will route to the self-hosted worker without needing a flag in every message.
Let me know which option works.
Hello, i have same issue and want slack integration to work with “my machine” worker
i am on private ultra plan. Not a team
and tried both options from docs and your advice
machine=devbox, private_worker=true, self_hosted=true
worker is started properly and accessible from ios application and from webui
But slack integration always tell me that it is not enabled:
This @CursorCursor mention requested a self-hosted cloud agent (self_hosted=true or pool=<name>), but your team has not enabled the self-hosted pool. Ask an admin to turn on Enable self-hosted pool in team settings, or remove the opt-in to run on Cursor’s managed infrastructure.
How to setup it properly with slack?
p.s. when i not mention private pool or machine it will be able to setup cloud agent, so cloud vm integration works,
but i want to reuse my own docker and network environment for execution
Hey, thanks for the detailed screenshots. Your setup looks correct, the workers are connected, and the pool is enabled. The issue isn’t your config, it’s how self-hosted agents work on different plans.
Quick overview:
- My Machines / Remote Control
agent worker start- Personal workers you can control from mobile and web. That’s what’s working for you right now.
- Self-Hosted Pool
pool=<name>- A centralized shared pool that requires Enterprise plus a service account API key.
The key point: self-hosted Cloud Agents via native triggers like Slack and Automations are gated at the team level. On a personal account without a team, routing Slack @Cursor to a self-hosted worker (both My Machines and pool) isn’t officially supported. That’s why you hit the team pool error even though your personal pool is enabled. Slack works with the Cloud VM because it doesn’t need a team or a pool.
So on an individual Ultra plan, this isn’t a setup problem, it’s a current limitation. To run Slack on self-hosted, you need a Team (for My Machines inside a team) or Enterprise plus a service account (for pool). I don’t have an ETA for individual account support.
Your use case is a strong argument, especially if it depends on local environment or hardware. Please add your vote and details here, this is the right thread for the request: Self hosting machine for automations in Pro
If there’s an update on individual self-hosted support, I’ll follow up.