I see PR indexing mentioned in the new pricing page, but not exactly sure what it is:
we are on the team plan so theoretically we can use it but unsure where to get it or how to turn it on etc
1 Like
I usually read PR to mean Pull Request in the software development world. But how it works and how you take advantage of it, I have no idea. Came here to learn the same thing.
Hey @greenfish6
Cursor can now index and fetch Pull Requests, much like files. Summaries of PRs appear in semantic search, and the agent can fetch specific PRs with a new tool.
You should have access after connecting your Github to Cursor.
Is there a way to disable this? Now, while using Cursor, I’m frequently getting ssh access requests iterating through all my keys - which means I need to enter my ssh password. I see this in the “Cursor Git Indexing” logs:
2025-06-27 11:53:20.379 [info] Creating Indexing Repo client: https://repo42.cursor.sh
2025-06-27 11:53:20.379 [info] Creating repo client with backend url: https://repo42.cursor.sh
2025-06-27 11:53:20.629 [info] Fetching repository at '<local_codebase_path>'...
2025-06-27 11:53:23.397 [error] Error while fetching repository: Failed to execute git {
"exitCode": 128,
"gitErrorCode": "RemoteConnectionError",
"gitCommand": "fetch",
"stdout": "",
"stderr": "sign_and_send_pubkey: signing failed for ECDSA \"<ssh_key_type>\" from agent: agent refused operation\r\nsign_and_send_pubkey: signing failed for ECDSA \"<ssh_key_type>\" from agent: agent refused operation\r\[email protected]: Permission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n"
}
2025-06-27 11:53:23.400 [info] Doing a startup handshake for git indexing.
2025-06-27 11:53:23.694 [warning] PR indexing denied by server: This feature is still rolling out and will be available soon.
2025-06-27 11:53:23.695 [error] Error during indexing setup: This feature is still rolling out and will be available soon.
This is incredibly frustrating! Hopefully this can be disabled in settings soon.
@arvindch
For PR indexing:
You should be able to disable PR indexing from the settings → VS code settings tab by searching and disabling:
cursor.semanticSearch.includePullRequests
For codebase indexing:
You can disable new folder indexing, as well as specify an ignore list for indexing:
This is done from the cursor settings → Indexing & Docs tab.
Hi @IsaacHopkinson, I truly think Git PR indexing should be distinctly configured from codebase indexing.
As far as I can tell, the settings you are pointing to are the latter right? I do not want to disable file/codebase indexing, only PR indexing - especially because I am not even using PRs for this codebase. Could you please provide a toggle for both seperately?
1 Like
Thanks for the callout @arvindch, my response was initially for codebase indexing, updated my response above to show the setting to disable PR indexing also.
1 Like
Thanks a bunch, happy this is possible to disable now. TBH it should’ve been disabled by default, but with a prompt to help drive adoption.
Is there a reason this is not within Cursor’s settings panel, but within the underlying Vscode settings panel? It would be great to have this in the same place you have file or semantic indexing for example, or the Github integration page.
@IsaacHopkinson how come PR indexing requires SSH key auth? I want to use the PR semantic search feature but don’t want cursor to automatically request SSH key access from my SSH agent. Can “automatically fetch on startup” be a separate setting?