Unreliable Github PR linking to change sets

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

When using an agent to create a PR on a remote repo that is integrated with GitHub, after merging the PR and asking the agent to make other changes, viewing the second round of changes links to the original (already merged) PR instead of the new PR.

This happens on IOS and the cursor ide (Mac - idk the version but it was just installed)

Steps to Reproduce

  • start an agent on a work space that represents a remote repo integrated via GitHub
  • ask the agent to make a PR → PR gets made (PR1) → merge the PR (from cursor)
  • ask the agent to make more changes (to the same files) → the agent does and a “change list” is provided in cursor → new draft PR is opened (PR2)
  • clicking on the new change list takes you to the previously created PR (PR1) that does not contain the new changes.

Expected Behavior

Selecting the change list and hitting view PR should take you to the new PR instead of the previous one.

Side note, there’s no way (that I know of) to view the open PRs in cursor besides clicking on the change list and hitting view PR. Because of this limitation, I often have to leave cursor to review PRs or prompt it again for open PRs.

Operating System

MacOS
Other

Version Information

For the ide, I don’t have the version unfortunately but i just downloaded it on Thursday.

For iOS: Cursor v1.4.0 (38998)

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report and repro steps. I reproduced it, and it’s a bug on our side. After merging the first PR, the View PR link on the new change set still points to the old merged PR instead of the new one. I reported it internally. I can’t share an ETA yet, but I’ll post an update in the thread as soon as I have one.

For now, workarounds:

  • After merging a PR, start a fresh agent for the next changes. Then the link should attach to the correct PR.
  • Or open the PR directly in GitHub.

On your side note about not being able to see open PRs inside Cursor beyond change list → View PR, that’s fair. I’ll pass it along as a separate feature request.

Let me know if the workaround doesn’t help, or if you notice anything else.