Still investigating for more details but I’ve found myself here several times. Strangely, uppercase/caps-lock still works.
Requires full restart of app from what I’ve found.
Keys work as-expected in all other apps.
Still investigating for more details but I’ve found myself here several times. Strangely, uppercase/caps-lock still works.
Requires full restart of app from what I’ve found.
Keys work as-expected in all other apps.
Hmm, this seems weird.
My initial guess is that it’s unlikely to be a bug in Cursor itself. Therefore, my first guesses would be:
When you say the keys don’t work, do you mean regarding keyboard shortcuts, or just typing those letters in general into the editor?
It seems to be cursor-specific and possibly related to the CMD+K bug I reported with @Documentation breaking all inputs (so far as i can recall the issue only happens after that bug has been triggered at some point)
I’m on an M3 mac, no computed software has changed. (I’m a freak about app-level keyboard shortcuts so i wouldn’t have anything that would affect system-level shortcuts).
However, in this case — it’s specifically around just typing in any Cursor inputs (including search, editor, etc) and not related to keyboard shortcuts.
Hey, it looks like an extension might be causing this. Try launching in disable-extensions mode and see if the issue persists.
what are you basing this off of?
Have you tried this? Most issues are not related to Cursor but to extensions, so it’s helpful to check if it works as expected without extensions.
Didn’t help.
Update: Seems possibly related to multi-window (cursor) setups which i often use across “workspaces” (macos).
The letters will work in some windows and not others.
For example — I may have:
I’ve noticed some keystroke will cycle my (MacOS) workspace back to focusing on a cursor-related input that may have been open in another window (say, composer, for example).
Let’s say I hit “backspace”. In some cases it behaves entirely normally. In other cases (tbd how to replicate exactly) it will randomly switch my MacOS workspace back to focusing on the editor where (for example) the composer is, and it will force the focus of my keystrokes to that input and start typing.
There’s a chance I am conflating the two issues but feel more confident than not that they are related.
Update: This is still happening but may have something to do with this “AI Notes” in cursor. If I have multiple MacOS workspaces open, with multiple monitors, holding shift on a symbol will switch to the primary MacOS workspace (the one that contains the terminal / primary sidebar / etc.
After this switch happens, this issue also is triggered.
Steps to reproduce / workaround (inconsistent):
It’s worth nothing that after this has happened once, it’s more likely to happen again with an annoying frequency until I restart the app completely (ie. not reload window).
Having said all of the above, there are other cursor-related windows that “hijack” the focus and also abruptly switch the focus to the primary editor, including:
Every time this abrupt focus-shift occurs, the lowercase letter issue follows.
Environment:
Multi-folder, single workspace using multiple monitors and multiple MacOS workspaces. I frequently will have numerous tabs/split editors open per MacOS workspace. To be clear, MacOS workspaces are effectively just separate windows but all running the same instance of the project — like opening a tab in a new window and maximizing it to another workspace.