Bug: The new `@Branch` context is not using the remote branch

Hello Cursor Team

I have been using the PR Diff context to craft pr descriptions and I noticed a problem after 0.49

Locally, I have changes in .vscode/settings.json file, which are not staged. When I use the @Branch, my changes are included which I think is not correct. It should completely ignore my local files and just focus on the state of the branch/remote branch.

On a slightly unrelated note, I think we definitely need the @Staged context. I have seen issues like Add "Diff of Staging Area" to @git command - #4 by mtf where I have a workaround to achieve what I want but I don’t want to waste any more tokens for forcing the agent to run something like git diff --staged | cat just to grab the changes in the staged files :slight_smile:

Locally Unstaged Changes

The Wrong Branch Diff Context

1 Like