Keys are detected twice

[AlbertoErcolani]

Describe the bug

Since version 0.58.0, every time I press a key in Lazygit, it is recognized, and the associated functionality is executed twice. All keys but arrow keys seem to be affected.

To Reproduce

Steps to reproduce the behavior:

1. Open Lazygit,
2. see repository with unstage files,
3. press 2 to focus on files,
4. press space on root folder,
5. briefly see all files being staged and immediately after, being unstaged. The log shows the pair of commands that have been executed.

Expected behavior

Each key is recognized, and its associated functionality is executed exactly once, when it is applicable.

Screenshots

Version info:

commit=1d0db51caf3d280a53f027ef049355fc9e0c57e8, build date=2026-02-07T08:34:27Z, build source=binaryRelease, version=0.59.0, os=windows, arch=amd64, git version=2.53.1.windows.1

Terminal info:

I am experiencing the issue both with Windows 10 default command prompt and the PowerShell.

[vaportail]

Indeed. Makes it unusable.

[stefanhaller]

In 0.58 we updated to a newer version of tcell, which no longer supports the initial Windows 10 version, and I suspect this may be the reason. Supposedly it still works with Windows 10 Creators Update (I have no idea what that is to be honest).

Since Windows 10 was EOL'ed last year, you want to update to 11 anyway.

[vortex-hue]

Hey @AlbertoErcolani, I’d love to jump in and tackle this double-key detection bug. I’ve spent a lot of time building Go-based CLI tools and dealing with terminal-level event handling, so I'm happy to dig into how the tcell update is interacting with the Windows console. I can work on a reproduction and see if we can implement a solid debounce or a fix for these input events to keep the Windows experience smooth. Let me know if I can get started!

[AlbertoErcolani]

Hello @vortex-hue, that's great news!
In fact, I was planning to stick to version 0.57.0 indefinitely (I am not going to upgrade to Win11) but a fix would be extremely appreciated.

Is there something I can do to help you with the reproduction?

[ijacek]

Having the same issue with Win 10. If you are working on it @vortex-hue , I can help with testing...

[stefanhaller]

If my suspicion is correct and the problem comes from tcell no longer supporting Windows 10 (before Creators update), then there won't be much we can do. We can't (or rather, don't want to) downgrade to an older tcell version, and "fixing" the problem on lazygit's end won't be possible if the support from tcell's side simply doesn't exist any more. For reference, the commit in tcell is gdamore/tcell@23917555a1ae45.

I may well be wrong of course, and this wasn't actually the problem. It's just a guess.

So the first thing we need is information from those running into the problem which Windows version you all are using (in particular, whether it's before version 1703, which I understand is the Creators update). And if so, why you can't update to a newer version.

[ijacek]

I'm running latest Win 10 22H2 with latest updates released in october 2025. My HW isn't supported by Win 11 so I'm not upgrading for time being.

The issue indeed appeared after that tcell update in Lazygit 0.58. If they say they switched support to the "new style VT console" then I guess I'm running it and the issue is there.

I'm using 0.57 so I'm fine for now and I understand that the support for EOL system is not a priority...

[AlbertoErcolani]

I am in ijacek's position.
My HW won't support Win11, I am running Win 10 22H2 with the latest update in October 2025.

[stefanhaller]

Ok, sounds like my guess is wrong then. Tcell should support your version of Windows 10, as far as I understand.

Maybe it's simply a bug in tcell then. I'm planning to update our tcell dependency to v3 soon (we're still using the latest v2 version right now), we should probably wait for that before investigating. Who knows, maybe it will make a difference.

[stefanhaller]

I have a preliminary branch that updates tcell to v3, it is called keybinding-revamp (no PR yet, there's still a bit more work to do for that). Could those who are having the issue please try it to see if the issue is still there with this build?

Also, I'd be interested which terminal you all are using, and whether changing to a different one (e.g. Windows Terminal vs. Alacritty) changes anything.

[ijacek]

I tested the keybinding-revamp, the issue is still there unfortunately.
I went back in history and it started at fec7e9 Bump gocui (and tcell) I guess that was the obvious suspect, right...?

I'm using mintty that comes with git installer, there everything behaves like each key event would happen twice, so for example pressing j jumps from first line to 3, then 5, etc.
When I tried cmd.exe then I see effect of each step, so I see it goes to line 2 and then immediately to 3, pressing again goes to 4 and then to line 5. So it seems the events are somehow duplicated and cmd.exe shows all of them but mintty shows just the final state.

I can help with testing if you would create a branch with debug logs or guide me where to look or what to change...

[stefanhaller]

@ijacek Thanks for testing. Could you also test if the issue occurs in Windows Terminal too, please? For the record, I remember I switched from MinTTY to Windows Terminal back when I was still using Windows 10, and found this to be quite an improvement in general (that's unrelated to this issue), so I recommend this anyway. You can easily run Git for Windows (git bash) in a Windows Terminal tab.

[ijacek]

Tried Win Terminal, it works well, it seems the issue never appeared there. Tested that old commit, master and keybinding-revamp branches, all ok.
There are several shells available and the issue never appears in any of them.

Another thing - most of the shells have laggy scrolling, probably because of updating the [0] panel but there is Windows PowerShell that has perfectly smooth UI response, I'll stick with this one from now on, thanks for recommendation :-)
To clarify, the laggy scrolling is in mintty, cmd.exe and most shells in Win Terminal, including old PowerShell, only the combination of Win Terminal and Win PowerShell is smooth...

Anyway, I can test any updates you make but for now I'll stick with WT and this bug is not an issue for me anymore.

Thanks for the effort.

[stefanhaller]

Good. In that case I'll consider this issue resolved; yes, it's a regression in 0.58.0 since it used to work in MinTTY and cmd.exe, and no longer does now, but I don't think it's a serious problem when Windows Terminal is better than those anyway.

If anybody isn't happy with this, feel free to dig deeper. You should then probably file an issue in the tcell repo to see if gdamore can do anything about it. I wouldn't hold my breath though, considering what he wrote here. I'm not going to spend any more time on this myself, in any case.

@AlbertoErcolani @vaportail Does that work for you too?