Leftover files `commit~xxx`

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have a lot of leftover files or virtual files that are incorrectly being scanned. They don’t appear to be in git or the file system.

Steps to Reproduce

Using an agent and then canceling their changes? I’m really not sure.

Expected Behavior

The files should not be scanned for issues.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.9
VSCode Version: 1.99.3
Commit: de327274300c6f38ec9f4240d11e82c3b0660b20
Date: 2025-08-30T21:02:27.236Z (2 days ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report.

These commit-xxxxx files are not generated in Cursor by default, but are usually created by 3rd party Git extensions, like GitHub Pull Requests or GitLens.

When you review a PR, open a file at a past commit, or enter “Review Mode,” the extension shows each file as it existed at each commit using a virtual filesystem. As these are treated as separate documents, you see many copies (one per commit) in Problems.

It depends on which extension is causing these issues to know how to resolve them:

  • GitHub Pull Requests: Command Palette → GitHub Pull Requests: Exit Review Mode
  • GitLens: Close any “Open Revision”/history editors
1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.