Issue Description:
Sometimes, the file explorer/tree area intermittently freezes or fails to expand subdirectories in Agent mode. This issue happens most frequently right after performing Git operations. It doesn’t happen 100% of the time, but when it does, the file tree simply stops responding and won’t show lower-level folders or files.
Steps to Reproduce
Use Cursor in Agent mode on Windows.
Execute some Git operations/commands.
Try to click and expand a folder in the file explorer panel.
Result: The sub-files or sub-folders fail to display.
Hey, this is a known issue with the file tree in Agent mode on Windows. It most often shows up after bulk operations or Git commands run by the agent. We’re already tracking it, there’s no ETA for a fix yet, but we’ve shipped a few fixes in this area over the last few weeks, so it should keep getting better.
Workarounds:
Reload Window Ctrl+Shift+P → Developer: Reload Window, after that the tree usually comes back
Collapse and expand the project root folder
A few quick questions so I can link your report to the right ticket:
After Reload Window, does the tree work normally, or does the issue come back right away?
Which Git actions trigger it most often commit, branch switch, stash?
If you have the Request ID from the agent session where it happened, please share it, it helps with debugging
Hey @hww just checking in. Since your report, we’ve shipped a few improvements around the file tree, and you’re currently on 3.5.17. The latest stable build is 3.7.21.
Can you update to the latest version via Help > Check for Updates, or download it from Cursor · Download, and let me know if the issue still happens after that? Some of the fixes in this area landed after 3.5.17, so there’s a good chance it’ll improve.
If the file tree still freezes after Git actions post-update, please share the details from my questions above:
After Reload Window, does the file tree work normally, or does the bug come back right away?
Which Git actions trigger it most often, commit, branch switch, stash?
The Request ID from the agent session where it happened, if you have it
That’ll help me tie your report down more precisely. I can’t give an ETA for a fix yet, but we’re actively working on this area.