Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I still wasn’t able to use the new Agent Window interface. It is completely broken. In the stable version it does not allow it to connect to WSL. When I upgrade to nightly, WSL is not longer a problem, but the “Open new terminal” does not work at all, neither self-hosted cloud agents. It asks me to connect to github even though it is self hosted.
Steps to Reproduce
Try to open terminal. Try to run self-hosted cloud agent
Expected Behavior
It should work
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
3.2.0-pre6
Does this stop you from using Cursor
Yes - Cursor is unusable
@Colin Any updates on this one?
Hi @Daniel_Weil,
Apologies for the delayed reply. You’re hitting three issues — let me break down the status of each:
1. Agent Window + WSL (stable) WSL support has been added to the Agents Window. Update to version 3.1.10 or later on Stable and the WSL install loop should no longer occur.
2. “Open new terminal” not working (nightly) - This may have been resolved alongside the WSL fix. After updating, try opening a terminal again. If it still doesn’t work, could you share a screenshot of the error? That would help us track it as a separate issue.
3. Self-hosted agents asking to “Connect GitHub” A fix for this has been shipped since you reported it. Self-hosted agents should no longer require a GitHub connection. Please update to the latest build, and the “Connect GitHub” prompt should no longer appear.
If any of these persist after updating, try logging out and back into Cursor, then let me know.
I also noticed you have a related thread about the same WSL issue — these share the same root cause, which is now resolved.
@mohitjain I tried verifying the item number 3, but it still does not work.
Can you clarify some things? We are using self-hosted workers because some of our projects are hosted inside gitlab and azure devops, and cursor’s cloud agents do not support very well these repos.
The issue that asked to connect to Github still occurs. I will attach an image.
I want to make sure that the self-hosted agents would work with any repo, or just github/gitlab? Can you confirm?
We want to setup workflows using Automations that each worker using an infraestrcture repo in github/gitlab would know how to checkout to other kinds of versioning providers, but I am wondering if it will be possible to use self-hosted cloud agents in our infraestruture in Kubernetes if the target code is not hosted in github/gitlab….
I am also wondering where in the new interface I can spawn these self-hosted cloud agents. I am guessing these features are not tested enough, because I can’t make them to work at all.
Thanks for all help,
Daniel
Apologies for the incorrect info in my last reply about item #3. The fix did ship, but your team still needs to be configured for the self-hosted bypass on our end. Could you email [email protected] mentioning that your team needs self-hosted agents enabled without the GitHub requirement? Our team can help you with that.
To answer your other questions:
Self-hosted agents with non-GitHub repos: Once enabled, self-hosted agents can work with any git repository accessible via HTTPS (GitLab, Azure DevOps, etc.). The worker uses its own git credentials, so it’s not limited to GitHub.
Spawning self-hosted agents in the new interface: The dropdown you’re seeing (Cloud / Self-hosted) is the correct place. Once the configuration is applied, selecting Self-hosted should show your registered worker’s repos in a dropdown instead of the “Connect GitHub” button.
Automations with non-GitHub repos: Self-hosted workers can clone from any HTTPS-accessible repo. However, PR-specific features (like starting an agent from a pull request URL) currently only support GitHub-style PR URLs. Basic repo checkout and branch operations work with any provider.
Hey @Daniel_Weil! WSL and terminal support in the Agents Window have been fixed in recent updates — please make sure you’re on the latest version. For the self-hosted agents config, the team at [email protected] can help get that set up.
For Dev Container support in the Agents Window, we’re tracking that in this thread — follow there for updates. Closing this one out.
