Cursor Automations go stale after repo rename

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Small bug: If you have Cursor Automations created to trigger on some event for a specific GitHub repo and that repo is renamed in GitHub, those automations no longer trigger for the new repo and need to be changed from the old repo name to the new repo name in the Automations section

Steps to Reproduce

  1. Create Cursor Automation on event for GitHub repo
  2. Rename GitHub repo in GitHub
  3. Automation stops triggering

Expected Behavior

I would expect the Automations to know when the repo is renamed and adjust accordingly

Operating System

MacOS

Version Information

Cursor Web 04/05/2026

Additional Information

I renamed my repo a couple weeks ago and didn’t know that my automations stopped running

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

This seems like a bug. Automations store the repo reference as a name/URL, and when the repo is renamed on GitHub, the stored reference goes stale.

For now, the workaround is what you’ve already found: manually updating each automation to point to the new repo name. I know that’s not ideal, especially if you have many automations.

Our team is aware of the broader class of repo-rename issues, and this has been flagged for the automation system specifically. Thanks for the clear report.

1 Like