Lagging a lot when typing commit msg

[haris-musa (Haris)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

This started after I updated to 2.6

Steps to Reproduce

In the git tab, type a commit message

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.6.11 (system setup)
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

[lodrixoll (Liam O'Driscoll)]

+1 bumping this. Am on WSL.

[Dorian_B]

Hi
it seems to be a general problem
https://forum.cursor.com/t/execrable-performance-on-windowsos-since-todays-update/153604/13

[deanrie]

Hey, this looks related to a wider performance issue on Windows after updating to 2.6. The team already knows about it and is collecting info in this thread: Execrable performance on windowsOS since today’s update.

So far, users have found a couple of workarounds:

1. Hide the chat panel Ctrl+Alt+B. A few users confirmed the lag goes away.
2. Close any agent chats that include file changes or diffs. They seem to be the main trigger for the memory leak.

If that doesn’t help, can you share:

• Is your chat panel open when you type the commit message?
• Roughly how much RAM is Cursor using in Task Manager?

Let me know how it goes.

[lodrixoll (Liam O'Driscoll)]

1. Hiding the chat panel decreases the lag, but does not fully remove the lag. There is still some lag when all panels are closed.
2. My cursor instance is using about 1,400 MB of ram

Still noticing this issue after installing most recent updates as of 03/09/26. Am on WSL.

[deanrie]

Hey, thanks for the info.

Good to hear the chat panel workaround helps a bit. Since you’re on WSL and the lag is still there even with the panel hidden, could you try a couple more things?

1. Open Process Explorer (Ctrl+Shift+P > Developer: Open Process Explorer) and check which process is using the most CPU or memory, especially extensionHost and ptyHost. If you can, please share a screenshot.
2. Run Cursor without extensions. In a terminal, run cursor --disable-extensions. If the lag goes away, an extension might be making things worse on WSL.
3. Close any existing agent chat tabs that include file changes or diffs, then open a fresh new chat.

The team is aware of a broader performance slowdown on Windows in version 2.6. Your note that it still happens on WSL after the latest updates is helpful and helps narrow down the cause.

Let me know what you see in Process Explorer.