Having issues creating a new Project in our Team account that will use a self-hosted machine instead of a cloud agent.
The project creates but gets stuck connecting to the running worker on our VM.
The worker is setup and working for regular chats via remote control.
Our account is setup to allow both personal and team self-hosted machines and requires them over cloud agents. Team setting for remote control is also enabled.
Steps to Reproduce
Create a new project and select an existing remote environment.
Expected Behavior
Project will create but progress will hang with this error: Waiting for self-hosted worker: No matching self-hosted worker is eligible for this run (attempt 10/40)
Hey @KyleAESI, thanks for the report — this is a team setting, not your machine.
With “Require Self-hosted Machines and Personal Machines” on, a Project pointed at a Cloud environment gets forced onto self-hosted but never targets your worker by name, so it waits forever. Two fixes:
In the Project’s machine picker, pick your machine directly (Remote Machines → My Machines → your worker) instead of the Cloud environment.
Or, an admin can turn off “Require Self-hosted Machines and Personal Machines” (cursor.com → Cloud Agents → Self-hosted Machines), leaving the other toggles on.
It’s not intended behavior and we’ve let the team know. Could you try option 1 and let me know if it starts? If it still hangs, drop the agent ID (bc-… from the URL).
Prior to submitting this forum post i did try option 1 already and explicitly selected the running self-hosted worker from the list but the project still fails to initialize. Furthermore, I have also tried setting up a project when the “require self‑hosted machines” setting is off for our team, and I was able to initialize the project. However, subsequent project chats where I’m targeting the self‑hosted machine to utilize that box for the compute of chats within that project also seem to intermittently fail.
Essentially, with the project’s workflow and honestly even other isolated non-project chats to my self-hosted machines, I’ve had very little success to get anything more than a couple prompts through.
Let me know if i can provide anything further that would aid the team.
When you start a project, in the init process, you can’t choose a machine to “run on”. That would become available only from the first agent, post init, which is as described stuck duo to no machine to work on.
We can’t ask admin to turn off “Require self hosted” as obviously it’s there for a reason - we don’t want to expose ourselves to cloud.
So what is needed is the option to designate a machine to “run on” on the project creation menu, and not just per-agent.