> In the recent update, the behavior of the Explorer pane seems to have changed. When I focus on the explorer and start typing, it automatically enters a “filter” mode (hiding files that don’t match) instead of the previous “highlight/navigation” mode (just jumping to the file without hiding others).
>
> I have tried setting “workbench.list.keyboardNavigation”: “simple” in my settings.json, which works in standard VS Code to disable the filter mode, but it seems to be ignored or overridden in Cursor.
>
> Request:
> Could you please provide an option to disable this automatic filtering or respect the workbench.list.keyboardNavigation setting? I prefer the classic behavior where typing just highlights the file without altering the view.
I’m running into the same issue. All the shortcuts I previously configured in the Explorer have stopped working. I’m honestly speechless. You guys added these features and enabled them by default, but why didn’t the release notes clearly explain how to disable them?
I genuinely don’t understand how this feature got approved for release. Did you not consider existing user habits at all? Is the Cursor PM just running out of things to do? You’re just shoving this disappointing feature down our throats. In VS Code, this defaults to a specific shortcut. But now, you guys at Cursor made it so pressing literally any key enters this mode. What were you guys thinking?
I’m actually thinking about quitting cursor altogether, more problems now than ever. Changing keybindings as they wish, freezing entirely on trying to confirm changes and etc even on m4 max.
Cursor team, please, provide the possibility to disable this fuzzy search in explorer pane. as of now, it’s impossible to use j,k to navigate (vim extension)
The recent UI/UX of Cursor is truly terrible.
They rushed the release too much and didn’t consider the development experience at all. It used to be better, but today I faced this problem and am considering quitting Cursor soon.
Yesterday I ran into the same issue. I use the Vim extension and navigate with J, K, H, and L. Since then I’ve been looking for an alternative; I’ve already spent several hours with no luck. I’m considering reverting the update. I’ll wait until next week, and if they don’t fix it, I’ll roll back the version and disable updates.
Ran into same issue today… Very disruptive for anybody using vim keybindings and any NERDTree-esque shortcuts to navigate around the explorer. Please please bring back an option to disable this
Little papercuts are starting to add up to make me think about going back to VSCode…
I truely don’t understand how a change like this happens? Why do we feel the need to differ from how VSCode works here? I imagine so many people have shortcuts here, as the explorer is one of the most-used views in VSCode besides the actual monaco code editors themselves.
