Desktop app “Build in Cloud” shows “No Git Remote” but repo is cloned from GitHub and web Cloud Agent works

[bunst]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m trying to use Build in Cloud from the Cursor desktop app on Windows, but I consistently get this error:

“No Git Remote
The cloud agent requires the Git repository to be hosted on GitHub/GitLab. Please add a remote to your Git repository and try again.”

However, my project is already a Git repo cloned from my personal GitHub account, and git remote -v clearly shows a valid GitHub remote. I can push and pull without any issues from this machine.

What’s confusing is that I have already set up a Cloud Agent environment for this same GitHub repo through the web interface, and that works fine — the web Cloud Agent can build and run the project as expected. I’d like to be able to use the same feature from the desktop app, since I prefer that interface.

Steps to Reproduce

Clone a GitHub repository from my personal GitHub account to my Windows machine (standard HTTPS clone).

Open the cloned folder (repo root) in Cursor desktop.

Confirm in the integrated terminal that:

git rev-parse --show-toplevel points to the project folder.

git remote -v shows the correct GitHub origin remote.

In Cursor desktop, create a build plan and click Build in Cloud.

Cursor shows the “No Git Remote” error, even though the repo is connected to GitHub and the web Cloud Agent for this repo works.

Expected Behavior

The desktop app should recognize that the current workspace is a Git repo cloned from GitHub with a valid origin remote.

Build in Cloud should be available and should reuse or create a Cloud Agent environment for this GitHub repo, just like it does when triggered from the web UI.

Operating System

Windows 10/11

Version Information

Version: 2.6.11 (user setup)
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

Git works fine locally (push/pull), and web Cloud Agent for the same repo works.

Confirmed that my GitHub account is connected in Cursor and that the Cursor GitHub app has access to my personal repos.

Restarted Cursor desktop and retried Build in Cloud.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the detailed report.

A few things to check or share so we can narrow this down:

1. Can you paste the exact output of git remote -v from the integrated terminal in Cursor? I want to see if it’s HTTPS (https://github.com/...) or SSH ([email protected]:...), and if it ends with .git.

2. Are you opening the project folder directly on Windows, or through WSL (Windows Subsystem for Linux)? There’s a known issue with Git detection through WSL paths.

3. In Cursor Settings (gear icon in the top right), under the GitHub section, can you confirm it shows your GitHub account as connected?

4. Also try this: close Cursor, then reopen it by right-clicking the project folder and selecting “Open with Cursor” instead of using File > Open Folder inside Cursor. After that, try Build in Cloud again.

Since the web Cloud Agent works fine for the same repo, your repo and GitHub setup look correct. This seems like a detection issue on the desktop side. Share the details above and we’ll go from there.

[bunst]

Dean, thank you for your reply.

1. C:\Dev\AutoCID>git remote -v
   origin https://github.com/bunkst8/AutoCID.git (fetch)
   origin https://github.com/bunkst8/AutoCID.git (push)
2. I’m not technical enough to understand this question. I open the folder in Cursor by going to File→Open Folder→Navigate with File Explorer to the repo folder.
3. The only reference to GitHub I see in Cursor for Windows is in Cloud Agents where all it says is to Manage Settings. That takes me to Cursor online. There, under Tools & MCP, it says “Connected as ‘bunkst8’ to repositories in GitHub organizations: bunkst8”. Under Cloud Agents, it shows that I have an environment set up and shows my GitHub repo. Does that answer your question?
4. There is no ‘Open with Cursor’ option in the file right click menu. See below screenshot.

Note: Cursor has updated since my original post. Below is the new version information.

Version: 2.6.19 (user setup)
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

[deanrie]

Hey, thanks for the follow-up, that all makes sense.

Your remote looks correct, and your GitHub connection via the web dashboard is fine. This is narrowing down to a detection issue on the desktop side.

A couple of things I want to clarify and try:

1. How exactly are you triggering Build in Cloud? In the Agent chat panel, there should be a dropdown below the input box where you can switch between Local and Cloud. Are you using that, or something else?

2. Try this sequence:

   • Open the Command Palette Ctrl+Shift+P
   • Type Cursor: Log In and make sure you’re logged into Cursor
   • Then open a new Agent chat, switch the dropdown to Cloud, and try again

3. Also, can you check: when you open the project in Cursor and run git remote -v in the integrated terminal, not an external terminal, does it still show the correct remote? I want to rule out any path mismatch between what Cursor sees vs your system terminal.

If none of that works, I’ll flag this as a bug with the team. Your web Cloud Agent setup works fine, so this is clearly a desktop-side detection issue.