Vim extension navigation keys (ijkl) not working in Explorer after Cursor 2.2.14 update

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In Cursor version 2.2.14, the Explorer (file browser) cannot use Vim extension navigation keys (ijkl) for movement. The same Vim extension works correctly in VSCode.環境資訊

  • Environment Information

    • Cursor Version: 2.2.14 (1685afce45886aa5579025ac7e077fc3d4369c50, arm64)
    • Vim Extension: [email protected]
    • Operating System: macOS (darwin 25.0.0)
    • Shell: zsh

Actual Behavior

Keys do not respond, cannot use Vim mode to control the Explorer.

Comparison Test

The same Vim extension works correctly in VSCode, confirming this is not an issue with the extension itself.

Impact

Medium - Affects workflow using Vim mode, but arrow keys can be used as an alternative.

Steps to Reproduce

  1. Install Vim extension (vscodevim.vim)
  2. Open the Explorer (file browser)
  3. Try to use j, k, h, l keys for navigation
  4. Keys do not respond

Expected Behavior

Should be able to use j (down), k (up), h (collapse), l (expand) to navigate in the Explorer.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.14 (Universal)
VSCode Version: 1.105.1
Commit: 1685afce45886aa5579025ac7e077fc3d4369c50
Date: 2025-12-11T01:12:35.790Z
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.0.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

6 Likes
4

Hey, thanks for the report. I’ll pass it to the team.

6

Please fix this issue, same here. Annoying bug !

1 Like
7

I attached a screenshot showing the problem, but I want to clarify that this is not a Vim extension issue.

What happens

When the Explorer sidebar is focused, any key press (letters like a, b, n, j, k, etc.) immediately opens the Find in Explorer search bar.

This happens even with:

  • Vim extension disabled

  • All custom keybindings removed (keybindings.json = )

  • workbench.list.automaticKeyboardNavigation = false

  • explorer.filterOnType = false

  • Clean settings.json

  • Full app restart

I also added new keybindings that should override everything, but even those are ignored because the Explorer always activates its “Find” mode first.

Why this looks like a Cursor regression

This behavior does not happen in:

  • VS Code

  • Zed

  • Antigravity

  • Older Cursor versions

Only Cursor 2.2.14+ forces the Explorer into a type-to-search state and consumes all keyboard events before user keybindings or Vim can process them.

Impact

  • Impossible to navigate Explorer with custom keys

  • Impossible to bind n → new file, or j/k for up/down

  • Explorer steals every keypress, making keyboard workflows unusable

  • Not related to Vim at all — the Explorer input handler is intercepting keys globally

Expected behavior

When “workbench.list.automaticKeyboardNavigation” is disabled, Explorer should not automatically open the Find bar, and user keybindings should take priority.

This looks like a regression in the Explorer/list navigation layer introduced in the latest update.

Screenshot 2025-12-11 at 17.00.07
Screenshot 2025-12-11 at 17.00.07271×400 19.7 KB

1 Like
8

Describe the Bug

After updating to Cursor 2.1.49+, VSCodeVim’s hjkl navigation keys stopped working in the Explorer panel.

Keyboard Shortcuts Troubleshooting Log:

[KeybindingService]: / Soft dispatching keyboard event
[KeybindingService]: \ Keyboard event cannot be dispatched
Info: [J]
      From 3 keybinding entries, no when clauses matched the context

VSCodeVim defines these keybindings:

{
  "key": "j",
  "command": "list.focusDown",
  "when": "listFocus && !inputFocus"
}

The when clause listFocus && !inputFocus is not matching the context anymore in Cursor 2.1.49+, even though the Explorer panel is focused.

Steps to Reproduce

  1. Install VSCodeVim extension
  2. Focus the Explorer panel (file tree)
  3. Press j or k to navigate up/down
  4. Run “Developer: Toggle Keyboard Shortcuts Troubleshooting” and check the log - shows “no when clauses matched”

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.48.9 (working: 2.1.48)
VSCode Version: 1.96.2
Note: Issue started in 2.1.49+, confirmed working in 2.1.48

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
9

please fix this asap, or at least give an option to customize this behavior.

10

Please fix this ASAP. I also have this issue after upgrading Cursor.

11

I have the exactly same issue. Please, please fix it.

12

Confirming this issue on Windows 11

13

Same problem - this really broke my workflow.

15

Same issue, please fix

17

Fixing it - we will disable search if vim bindings enabled

1 Like
Option to disable "Type to Search" / Filter in Explorer pane (Revert to simple highlight)
18

Is this just using the vim extension (Vim - Visual Studio Marketplace)?

1 Like
19

I’m also using VSCode Neovim - Visual Studio Marketplace

1 Like
20

It has been resolved now.

1 Like
21

I’m using VSCode Neovim - Visual Studio Marketplace +1

22

This problem was just fixed and has returned again. Damn it.

24

Hey, what version of Cursor do you have?

25

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

This issue: Bug Report: workbench.list.typeNavigationMode is not working properly (search always automatic) · Issue #3867 · cursor/cursor · GitHub

It’s not fixed for me on the latest build. I am using the vs-code neovim extension and cannot navigate my file tree with this auto search behaviour happening. I tried setting “workbench.list.typeNavigationMode”: “trigger” but that hasn’t helped

Is not resolved for me.

Steps to Reproduce

Open the file tree, try to use h j k l to navigate with vscode-neovim extension installed

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.30
VSCode Version: 1.105.1
Commit: 6b030be1a256f7464cbd98e48627a802a4831bf0
Date: 2025-12-17T06:31:05.530Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

26

This issue has appeared again. There are now serious concerns about the overall product quality.

Version: 2.2.35 (Universal)
VSCode Version: 1.105.1
Commit: 86d7e0c1a66a0a5f7e32cdbaf9b4bfbaf20ddaf0
Date: 2025-12-18T04:28:48.652Z
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.1.0