Renaming GH Repository (and org?) breaks cloud agent GH access

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I recently had an org named “revel8-io” and repo named “revel8-explorer” in GH.
When I changed my org to “hivemindhq-io” and repo to “hivemind-explorer” in GH it appears to have broken the ability for me to connect my cloud agents via Cursor IDE.

Steps to Reproduce

Connect a GH account and repository, then rename the org and repository and see if you can connect the GH account / repo in the “Cloud Agents” Cursor IDE settings

Expected Behavior

Should connect just fine and allow user to start using Cloud Agents

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.35
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z (4 days ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. I can see the issue in the screenshot. Cloud Agent is still looking for the old repo name (Revel8-io/revel8-explorer) instead of the new one.

Try this workaround:

Let me know if the issue is still there after reinstalling.

I figured it out… I kept wondering why revel8-io/revel8-explorer kept showing up as a “Repository” in those settings even though I had renamed it on GitHub and the issue was that the REMOTE origin for my Git CLI had the old repo still set as the origin.

kylan@redacted hivemind-explorer % git remote -v
origin  [email protected]:revel8-io/revel8-explorer.git (fetch)
origin  [email protected]:revel8-io/revel8-explorer.git (push)

kylan@redacted hivemind-explorer % git remote remove origin

kylan@redacted hivemind-explorer % git remote add origin [email protected]:hivemindhq-io/hivemind-explorer.git

I was wondering why it kept scanning for that repo even when there was no trace of it in the repository when I search around for it. Apparently that was the issue

Hey, glad you got it figured out! Yeah, that’s exactly the reason. Cursor reads the config from the local Git remote, so the old URL kept being used even after the repo was renamed on GitHub.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.