Staged Git changes disappear in multi-root workspace after Pylance uninstallation and restart

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Operating System

  • OS: Linux Mint

Cursor Version

Version: 1.5.11
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.0-79-generic

Describe the Bug

When working in a multi-root workspace (a single folder containing multiple Git repositories), the Source Control panel fails to display staged changes for some of the repositories after the editor forces the uninstallation of the ms-python.vscode-pylance extension and performs a restart. The staged changes are not lost—they are still present and visible when running git status from the command line or when opening the affected repository in its own separate Cursor window. The issue appears to be a UI/indexing bug specific to the multi-root workspace view.

Steps to Reproduce

  1. Open a folder in Cursor that contains multiple, separate Git repositories (e.g., ~/Projects/ which contains ~/Projects/repo-A, ~/Projects/repo-B, and ~/Projects/repo-C).
  2. Ensure one of these repositories is a Python project and that you have the ms-python.vscode-pylance extension installed.
  3. In repositories repo-A and repo-B, make changes to some files and stage them using git add .. The changes should be visible in the “Staged Changes” section of the Source Control panel.
  4. Trigger the prompt from Cursor that requires ms-python.vscode-pylance to be uninstalled in favor of anysphere.[cursor](https://forum.cursor.com/c/bug-report/6)pyright.
  5. Accept the “Uninstall and Restart” option.
  6. After the editor restarts, observe the Source Control panel.

Expected Behavior

After the restart, the Source Control panel should correctly display the staged changes for all three repositories (repo-A, repo-B, and repo-C) within the multi-root workspace view.

Actual Behavior

After the restart, the Source Control panel only shows the Git status for one of the repositories (in my case, the Python project). The staged changes for repo-A and repo-B have vanished from the UI. The Source Control view acts as if there are no changes in those repositories.

Workaround and Verification

  • The “lost” staged changes are immediately visible again if I close the multi-root workspace and open the folder for repo-A or repo-B directly in a new Cursor window.
  • Running git status in the terminal for each repository correctly shows the staged files, confirming that no data was actually lost.
  • Closing and re-opening the entire multi-root workspace folder does not resolve the issue.

This seems to be a caching or indexing issue in the Source Control view for multi-root workspaces, triggered by the forced restart during the extension migration.

Steps to Reproduce

Open a folder in Cursor that contains multiple, separate Git repositories (e.g., ~/Projects/ which contains ~/Projects/repo-A, ~/Projects/repo-B, and ~/Projects/repo-C).
Ensure one of these repositories is a Python project and that you have the ms-python.vscode-pylance extension installed.
In repositories repo-A and repo-B, make changes to some files and stage them using git add .. The changes should be visible in the “Staged Changes” section of the Source Control panel.
Trigger the prompt from Cursor that requires ms-python.vscode-pylance to be uninstalled in favor of anysphere.[cursor](https://forum.cursor.com/c/bug-report/6)pyright.
Accept the “Uninstall and Restart” option.
After the editor restarts, observe the Source Control panel.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.11
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
Electron: 34.5.8
Chromium: 132.0.6834.210

3

I am having the same issue. I’ve uninstalled ms-python.vscode-pylance and it’s still happening, so I’m not sure it’s related to that or not.

5

Still experiencing this on Cursor v1.6.45

7

Also, more context, I’m experiencing this issue in a non-python workspace; my two projects are PHP and Javascript. Only PHP project showing changes in the Source Control tab

9

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