Cloud Environments + GitHub Repo Renaming Issues

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Cloud Agents: environments can’t follow a GitHub repo rename

We renamed a Github repo. The environment is still tied to the original name, and there’s no way to change its repo, or the repo a Project uses, without creating a new environment and starting a new Project. GitHub’s redirect keeps clone, push and create-PR working. Updating a PR is refused with “PR URL must belong to the current repository”, because the new URL doesn’t match the environment’s repo name.

Asks:

  • Let us edit an environment’s repository, or pick up renames automatically from GitHub’s repo ID.
  • Let a Project switch to another environment.
  • Until then, have the PR tool resolve renamed repos through the GitHub API instead of comparing names.

Steps to Reproduce

  • Create a repo
  • Create the Cursor environment
  • Rename the repo
  • The environment doesn’t reflect the renamed repository in both UI (and tool usage above)

Expected Behavior

Either detect the rename, or allow a manual rename in the UI.

Operating System

MacOS

Version Information

Version: 3.22.12
VS Code Extension API: 1.128.0
Commit: 3a92974361033b2051526321308c2740fe5912c0
Date: 2026-09-26T04:55:12.125Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 27.0.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey @Elliot_Hesp, thanks for the clear write-up.

You’re right about the cause. An environment keeps the repo name it was created with, so after a rename, PR updates are checked against the old name and refused. This isn’t caused by anything in your setup, and it’s an issue we’re tracking. I’ve also passed along your asks about following renames, editing an environment’s repo, and switching a Project’s environment.

Workarounds for now:

  1. For existing PRs, have the agent update the PR using the full link with the old repo name (e.g. github.com/your-org/old-name/pull/123). I tested this, and the update goes through to the renamed repo. Updating by branch name alone still fails, so it needs the full link.
  2. For new work, create a new environment on the renamed repo and start new Projects from it.

I’ll post here with any relevant updates!