Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Original thread: Search shortcut not working after a while
If you have an agent generate a plan using “Plan Mode” and then close that plan, CMD + F (to search through your code) will randomly stop working on your open files.
Steps to Reproduce
Not positive if these are the exact steps, but:
- Generate a plan in plan mode.
- Work in your files, etc., without actually executing / building the plan.
- close all open files/tabs.
- Open a file, try to find code in your file.
- The “find” functionality will not work (no search box opens up in the corner of your active editor).
I debugged this using Cmd + Shift + P > “Developer: Toggle Keyboard Shortcuts Troubleshooting” and it output this log message:
[info] [Window] [KeybindingService]: / Soft dispatching keyboard event
[info] [Window] [KeybindingService]: \ Keyboard event cannot be dispatched
[info] [Window] [KeybindingService]: / Received keydown event - modifiers: [meta], code: MetaLeft, keyCode: 91, key: Meta
[info] [Window] [KeybindingService]: | Converted keydown event - modifiers: [meta], code: MetaLeft, keyCode: 57 ('Meta')
[info] [Window] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[info] [Window] [KeybindingService]: / Soft dispatching keyboard event
[info] [Window] [KeybindingService]: | Resolving meta+[KeyF]
[info] [Window] [KeybindingService]: \ From 13 keybinding entries, matched planEditor.actions.find, when: markdownPlanEditorActive, source: built-in.
[info] [Window] [KeybindingService]: / Received keydown event - modifiers: [meta], code: KeyF, keyCode: 70, key: f
[info] [Window] [KeybindingService]: | Converted keydown event - modifiers: [meta], code: KeyF, keyCode: 36 ('F')
IE, it resolved to planEditor.actions.find, even though I had closed all plans.
Expected Behavior
planEditor should not be active if I don’t have a plan actively selected.
Operating System
MacOS
Version Information
Version: 2.4.28 (Universal)
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z (3 days ago)
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
No - Cursor works, but with this issue