Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I use Cursor because my company is on a team plan. If the choice were mine, I would have uninstalled it already. A paid editor should make it easier to work. Instead, I had to spend my time tracing Windows process trees to find out why Git kept running in the background while my machine was barely usable.
Here’s what I captured on Windows with Cursor 3.27.22 installed:
- Between 10:50 and 10:54, Cursor’s GlassDiffService logged 53 Failed to execute git errors against the same local workspace.
- At 10:53:13, Cursor logged that its local extension host, PID 29880, was unresponsive.
- A process snapshot taken before reboot showed that same extension host as the parent of a Windows git.exe running git diff --raw --numstat. That process had a Git child running the same command.
I can trace those Git processes directly to Cursor. The snapshot doesn’t establish how much of the total CPU and memory load they accounted for. It does show an editor repeatedly failing to refresh Git diffs during a slowdown, with no obvious way for me to tell it to stop.
Give us a dedicated setting to turn off Cursor’s background Git diff refresh. Document exactly what git.autorefresh and git.enabled control in Cursor. When a refresh keeps failing, back off and stop stacking redundant work. Let me request a diff when I actually need one.
My company is paying for a tool I’m expected to use every day. I shouldn’t need PowerShell, process IDs, and renderer logs just to figure out why an idle editor is still launching Git.
Steps to Reproduce
I use Cursor because my company is on a team plan. If the choice were mine, I would have uninstalled it already. A paid editor should make it easier to work. Instead, I had to spend my time tracing Windows process trees to find out why Git kept running in the background while my machine was barely usable.
Here’s what I captured on Windows with Cursor 3.27.22 installed:
- Between 10:50 and 10:54, Cursor’s GlassDiffService logged 53 Failed to execute git errors against the same local workspace.
- At 10:53:13, Cursor logged that its local extension host, PID 29880, was unresponsive.
- A process snapshot taken before reboot showed that same extension host as the parent of a Windows git.exe running git diff --raw --numstat. That process had a Git child running the same command.
I can trace those Git processes directly to Cursor. The snapshot doesn’t establish how much of the total CPU and memory load they accounted for. It does show an editor repeatedly failing to refresh Git diffs during a slowdown, with no obvious way for me to tell it to stop.
Give us a dedicated setting to turn off Cursor’s background Git diff refresh. Document exactly what git.autorefresh and git.enabled control in Cursor. When a refresh keeps failing, back off and stop stacking redundant work. Let me request a diff when I actually need one.
My company is paying for a tool I’m expected to use every day. I shouldn’t need PowerShell, process IDs, and renderer logs just to figure out why an idle editor is still launching Git.
Operating System
Windows 10/11
Version Information
Cursor 3.27.22
Does this stop you from using Cursor
Yes - Cursor is unusable