Can't "Build in Cloud" after renaming repository

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I renamed my repository (moving it from personal account to org account), updated the local git checkout, and also removed and reinstalled the Cursor integration on my Github repo, but when I try to do “Build in Cloud” from IDE, I get an error that no environment was found for the old repo name. So Cursor apparently has stashed the repo name somewhere that isn’t being updated.

Steps to Reproduce

  1. Work in repo with Cursor IDE
  2. Rename repo
  3. Make a plan and select “Build in Cloud”

Expected Behavior

I expect a cloud agent to kick off to implement the plan

Operating System

MacOS

Version Information

Version: 2.6.22
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey, this is a continuation of the same issue you mentioned in this thread: Renaming repo breaks Cloud Agent environment, making existing agents read-only. Cloud agent environments are tied to the repo URL when they’re created and don’t get updated after a rename. Build in Cloud still looks up the environment under the old name, which is why you’re seeing the error.

The team is aware and the bug is logged, but there’s no timeline yet.

As a workaround, try deleting the environment for this repo at cursor.com/settings and then recreating it. It should bind to the new URL.

Let me know if that fixes it.