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.
With Require Self-hosted Machines and Personal Machines on, setting up a new Project can’t use a personal machine started with agent worker start right now, so it keeps waiting. It isn’t intended, and we’ve let the team know.
For now:
On an Enterprise plan: run the machine as a Team Pool worker. Projects can use pools with Require on.
Otherwise: turn Require off while you create the Project.
@KyleAESI, for the Project chats that fail on your machine with Require off, could you share an agent ID (the bc-... part of the URL) and roughly when it happened?
I found what is happening here! Your team has “Require Self-hosted Machines and Personal Machines” enabled, so every agent you start is routed to your self-hosted machines, even when the Project is pointed at a Cloud environment. A personal machine (the one you run with agent worker start, which appears under My Machines) is picked up only when the run explicitly targets that machine. A run that is pointed at a Cloud environment does not do that, so it waits for a machine that never becomes eligible. That is why remote control chats work (they target the machine directly), but this Project does not.
Two ways to get unblocked right now:
In the Project’s environment picker, choose your machine directly instead of the Cloud environment: open the picker, go to Remote Machines, then My Machines, and select devbox-1 (or whatever your worker is named). Then create the Project.
If you want to keep using Cloud environments as well, a team admin can turn off “Require Self-hosted Machines and Personal Machines” on cursor.com under Cloud Agents, Self-hosted Machines (leave “Enable Self-hosted Machines” and “Enable Remote Control for Team” on). Runs you point at your machine will still run there.
Can you try option 1 and let me know whether the Project starts on your machine? If it still hangs, reply with the agent ID (the bc-… part of the URL) and the time you tried.Hey @KyleAESI,
This has been addressed on our side and will be rolled out soon if it hasn’t been already. With “Require Self-hosted Machines and Personal Machines” on and no team pool, setting up a new Project will now use your own connected machine instead of waiting on “No matching self-hosted worker is eligible for this run”. You can leave Require on, and no app update is needed.
Could you give Project creation another try and let me know if it still gets stuck?
Separately, if chats on your machine still fail intermittently after that, an agent ID (the bc-... part of the URL) and roughly when it happened would help us dig in.
Hey @Oren_Kishon, you’re right, sorry for the confusion. There’s no machine picker when you create a Project (the Create Project dialog only has Workspace and Model), so please ignore that first suggestion in my last message.
You shouldn’t need one anymore, though. With the change I mentioned, when your team requires self-hosted machines and no team pool machine is available for the repo, Project setup now runs on your own connected machine automatically. You can leave Require on.
To try it:
On your machine, start the worker (agent worker start) from a checkout of the repo you want the Project to use.
On cursor.com, open Cloud Agents and confirm the machine shows as online under My Machines.
In the Agents Window, create a new Project and pick that repo under Workspace.
Watch the setup. It should start on your machine within a few seconds instead of showing “No matching self-hosted worker is eligible for this run”.
Once the Project exists, the “Run on” menu at the bottom of the Project chat lets you choose which machines its agents can use. Each new agent in the Project also has its own picker (Cloud, Remote Machines, My Machines).
If setup still gets stuck, reply with the agent ID (the bc-… part of the URL) and the time you tried, and we’ll take a look.
It worked, thank you. Step 4 did succeed - it picked up the remote machine from the Project creation - through the selection of the workspace (I guess).