Commit message box lagging

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Last couple of updates, the commit message form field has a weird lag when you’re typing, takes several seconds to print what you’re typing.

Steps to Reproduce

type a commit message/title

Expected Behavior

no lag

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 2.6.13
VSCode Version: 1.105.1
Commit: 60faf7b51077ed1df1db718157bbfed740d2e160
Date: 2026-03-06T06:17:49.499Z (1 day ago)
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: Darwin x64 23.6.0

For AI issues: which model did you use?

any / opus 4.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Hey, thanks for the report. A couple things to try:

  1. Run Cursor from the command line with extensions disabled to rule them out:

    cursor --disable-extensions
    

    If the lag disappears, one of your extensions is causing it. You can narrow it down by enabling them one by one.

  2. If it still lags without extensions, open the Process Explorer (Cmd + Shift + P > Developer: Open Process Explorer) while typing in the commit box, and share a screenshot of what’s using CPU.

Also, about how many changed files do you usually have staged when you notice this? And how big is the repo?

Let me know how it goes.

I’m having the same issue. Unfortunately I can’t really disable extensions in my use case as I develop in devcontainers and need the Dev Containers extension to do so.

I did disable all features and extensions in my devcontainer and still found the issue to be present.
Interestingly though, the issue disappears the moment I open the Process Explorer window. I’ve tried this multiple times, and given Cursor enough time after starting to ensure it wasn’t a coincidence. I’m able to type normally in the commit message box the moment I open the Process Explorer window.

After further testing it actually seems that it’s the moment I open the Command Palette that it fixes the laggy input, not when I open the Process Explorer. I reenabled all features and extensions in my devcontainer and found the same behavior. The laggy input in the commit message box disappears after opening the Command Palette for me. Could work as a temporary workaround until the issue is resolved @paulmontreal .

2 Likes

ha. that works. very strange. might help them find a fix. (I’m not using any extensions that I’m aware of)
thanks for the tip. @celestialorb

@deanrie did you catch the comment on this from @celestialorb ?
simply clicking in the top panel where the command palette opens fixes the huge lag bug in commit message box. might give your guys some clues as to what the bug is.

Yes, I saw it. Really helpful find from @celestialorb. The fact that the lag goes away after opening the Command Palette is a great clue for debugging.

I passed this on to the team.

1 Like

I can confirm I have the same issue, with the same fix (thanks for the fix BTW !). I’m running Cursor 2.6.19 on nixos.

This issue is still happening in 2.6.20 on Ubuntu. It’s one of those annoying little things that introduce friction…

I had to restart the cursor everytime, after this lag issue. Its really annoying and frustating when you finish the work and try to commit the changes with that lag. Hopefully the restart was fixing the issue but this is really helpful @celestialorb Thanks.