degi
(Degi)
October 23, 2025, 6:14am
1
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Using h/j/k/l to navigate is so slow it’s basically unusable .
The cursor moves slowly, lags, and jumps around instead of scrolling smoothly.
Steps to Reproduce
Install vscodevim.vim extension and try to move your cursor on the editor in normal mode.
Expected Behavior
It was fast, and smooth
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.7.54
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
deanrie
(Dean Rie)
October 23, 2025, 12:39pm
2
Hey, thanks for the report. Vim navigation lag can have different causes. Help us narrow it down:
Please share:
Check Extension Monitor Cmd+Shift+P → “Developer: Open Extension Monitor” what’s the CPU/memory usage for VSCodeVim?
What file type and size are you editing when this happens?
Do you have other extensions installed?
Let me know what you find.
degi
(Degi)
October 24, 2025, 6:36am
3
this command doesn’t exists.
Any file size, and any file type. Markdown file 50 lines, or Typescript file with few hundred lines, all laggy.
Yeah, I have so many other extensions installed, but it was there for all the time. And it was fine until recently.
deanrie
(Dean Rie)
October 24, 2025, 1:31pm
4
Ah, sorry, you need to enable the experimental feature.
degi
(Degi)
November 3, 2025, 8:34am
5
It says zero for everything
hicder_rbx
(Hieu Pham)
November 12, 2025, 9:33pm
6
I have the same problem. It started happenning due to recent Cursor update I believe. 2 months ago vim mode is pretty smooth.
dmarkow
(Dylan Markow)
November 14, 2025, 12:41pm
7
Same issue, also started recently. Looking at the cursor tab logs:
When I hold down the down key to scroll through a file, cursor doesn’t send a tab completion request until I let go
When I hold down j instead to scroll down, cursor tab repeated fires requests for almost every line. Just tried it in a 500 line file, and it fired off around 450 requests.
1 Like
hicder_rbx
(Hieu Pham)
November 15, 2025, 1:45am
8
does disabling Cursor Tab fix the issue for you? it’s still pretty laggy for me even when I disable Cursor Tab
in latest cursor, it’s still not fixed (even though it does seem to get better). I really hope it gets fixed.
0xFA11
December 18, 2025, 5:49pm
10
FWIW, I’m on current latest Cursor on Mac and having this issue while navigating around a file with jk and other vim motions.
I also want to repeat what @hicder_rbx said above, it wasn’t happening a few months ago and some update along the way started to cause this issue.
It’s sadly a productivity/flow killer for me
Version: 2.2.36
VSCode Version: 1.105.1
Commit: 55c9bc11e99cedd1fb93fbb7996abf779c583150
Date: 2025-12-18T06:25:21.733Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0
0xFA11
December 24, 2025, 1:00pm
11
@deanrie should we create a new post for this issue or keep this one to track it? I’m worried by the fact that this post was created at October 2023 and one way or another, the issue still exists - makes me think it’s not tracked or prioritized at all
1 Like
hicder_rbx
(Hieu Pham)
January 24, 2026, 1:51pm
15
Describe the Bug
Vim mode (through vscodevim.vim extension) is very laggy when scrolling with j/k. If I disable this extension and scroll with arrow key up/down, it’s smooth.
It isn’t used to be this way, and things seem to change when Cursor 2.0 was introduced.
Please make it smooth again.
Steps to Reproduce
Install vscodevim.vim extension, then try open a large file, and scroll up and down with j/k
Expected Behavior
It should be smooth
Operating System
MacOS
Version Information
Version: 2.4.21
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0
Does this stop you from using Cursor
Yes - Cursor is unusable