Can't start cloud agent from IDE or use "Build in Cloud" after renaming repository

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

NOTE: I already posted this bug in another thread (Can't "Build in Cloud" after renaming repository), and @deanrie responded and then asked for follow up, but closed the thread so I can’t reply there. Reposting here because I don’t think my original post was clear enough.

Original bug report:

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 start a cloud agent or do “Build in Cloud” from IDE, I get an error that no environment was found for the old repo name. So Cursor IDE apparently has stashed the repo name somewhere that isn’t being updated.

To be clear, I already have an environment setup for cloud agents under the new repo name, and I can spin up cloud agents from cursor.com/agents or use automations without issue. The problem here is that the local Cursor IDE has stashed somewhere that the project I’m working on is at the OLD repo name, and I can’t figure out where. Presumably I could completely uninstall and wipe Cursor IDE caches and reinstall, and then it’d work fine, but I’d like to avoid that.

Where would Cursor IDE have stashed the repo URL for this project such that it’s trying to instantiate a cloud agent using the old repo URL instead of the new one?

Steps to Reproduce

  1. Work in repo with Cursor IDE
  2. Rename repo
  3. Make a plan and select “Build in Cloud” or start a cloud agent from the IDE

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

Additional Information

Cloud Agents work fine, my environment is all setup for the cloud agents, it’s just that the Cursor IDE has a reference to the old repo url and I can’t figure out where!

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Feel a little dumb, but I just had Cursor take a crack at this, here’s its summary of what it found:

Problem: After renaming/transferring a GitHub repository (e.g. from personal-account/my-repo to my-org/my-repo), updating the git remote locally, and reinstalling the Cursor GitHub integration, “Build in Cloud” and cloud agent launches from the IDE fail with an error saying no environment was found — because it’s still looking for the old repo name. Cloud agents work fine when launched from cursor.com or via automations.

Root cause: Cursor caches the GitHub repository URL in two SQLite databases on disk, and these cached values are not updated when the git remote changes:

  1. Workspace-specific state DB (~/Library/Application Support/Cursor/User/workspaceStorage/<workspace-id>/state.vscdb): The key workbench.backgroundComposer.workspacePersistentData contains a cachedSelectedRemote object with the old repo URL. This is the direct cause — it’s what “Build in Cloud” uses to determine which repo to target.

  2. Global state DB (~/Library/Application Support/Cursor/User/globalStorage/state.vscdb): The key repositoryTracker.paths maintains a mapping of GitHub repo paths to local directories. After a rename, the old entry persists alongside any new one.

Ideally Cursor should detect when the git remote has changed and update these cached values automatically, or at minimum provide a UI to clear/reset the cached remote.

It gave me some sqlite3 commands that fixed the issue!

7

Hey, sorry the previous thread got closed before you had a chance to reply. That wasn’t supposed to happen.

Great find with the SQLite databases. You’re right, this is a client-side root cause. The IDE caches the repo URL in workspaceStorage and globalStorage state.vscdb and doesn’t update it when the remote changes. Glad the sqlite3 commands helped.

This is a known issue and the team is aware. Ideally the IDE would automatically pick up changes from git remote, but it doesn’t yet. Your findings will definitely help with prioritization, thanks for the detailed breakdown.

Let me know if anything else comes up.

1 Like