Using the above setup, I cannot launch a new agent using my machines from the cursor 3 agent window. The only way for me to actually use this is to start threads on the web view at cursor.com/agents then switch the to desktop app when its started. This seems either like an wild oversight or a deliberate step to not support it.
I am looking for a way to manage many background agents - This is the only way I can use dev containers because Dev container remotes don't work with Glass still has no ETA.
After digging in further, you’re right. Currently, the Agents Window will only pick up pool workers, not specific machines. As a workaround, you can run agent worker start --pool, though this means only one cloud agent can claim your worker at a time.
Hi Colin - as of today I am seeing my machines on Cursor 3. However, this now has a connect to github prompt that appears to be a bug (we have gitlab connected - this is working on web view)
Good to hear that My Machines is now showing in Cursor 3.
The “Connect GitHub” prompt showing when you’re using GitLab is a known bug our team is aware of. In the meantime, if your machines are visible and functional otherwise, you should be able to work around this by ignoring the prompt.
