Build plan gots stuck to no remote error after I tried to start Build on Cloud on a new git project folder

[Emre_Koc]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I tried to start a Build process after a build plan is prepared by Composer 1 model. This was a project that I recently created while model was preparing the build plan I added a github remote to the project folder. After build plan is ready I clicked Build on cloud button. It showed me a warning that I needed a remote on github for that feature. I already had it but it didn’t get that info i guess. after this build button gone and what every I try to do on that same windows it started to show the same no remote warning. Even I try to click Build locally button in plan document it still shows no remote warning.

Steps to Reproduce

Create a private repo on Github
Create a new folder on your mac
Open folder in Cursor
Start a build plan for any type of project
After it finishes that plan init git on the project folder and add remote
Click Build on Cloud button.
It should show a warning that project does not have a remote.
Try to build plan locally, it should still fail.

Expected Behavior

If a project does not have a remote it should not show Build on Cloud option.
Even it shows it, it should not get stuck after we click Build on Cloud option and allow us to build locally.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.64
VSCode Version: 1.99.3
Commit: 25412918da7e74b2686b25d62da1f01cfcd27680
Date: 2025-11-06T04:35:14.424Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.0.0

For AI issues: which model did you use?

Composer 1

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. It looks like a UI state bug - Cursor isn’t refreshing the git remote status after you add it.

Try:

• Fully restart Cursor
• Open a new chat and create a fresh build plan

Also verify:

• Run git remote -v to confirm the remote exists
• Ensure the Cursor GitHub app has read–write access for this repo (Cursor Settings → Cloud Agents, or in your GitHub app permissions)

You’re right - either “Build on Cloud” shouldn’t show initially, or the remote status should refresh before building. Local builds definitely shouldn’t be blocked by this.

Does restarting or creating a new chat help?