I am on MacOS. After I restarted my Cursor, it automatically upgraded to 3.0.13. Now my usual keyboard shortcut does not work anymore.
For example:
"cmd + " does not split the editor anymore.
“cmd + ctrl + right” does not split and move the file to the next group anymore.
“cmd + option + right” or “cmd + option + left” does not move the file focus to the next or previous file anymore.
I have tried to manually set the binding via the setting as well as by editing the JSON. But this does not have any effect even after restarting the IDE.
Please provide a solution as it is annoying having to retrain my muscle memory for keyboard shortcut habit.
Steps to Reproduce
Just upgrade cursor version to 3.0.13
Expected Behavior
The keyboard shortcuts remain as is, as the ones before the 3.0.13
Hey, thanks for the report. A couple quick questions so we can figure out what’s causing it:
Do the shortcuts fail all the time, or only when focus is in the chat or composer panel? Try clicking into the code editor area, then press Cmd+\. Does it work?
Open Cmd+Shift+P > Developer: Toggle Keyboard Shortcuts Troubleshooting, then press the shortcut that isn’t working. A log will show up at the bottom, please share a screenshot of what it shows.
Try launching Cursor from Terminal with cursor --disable-extensions. Does the issue still happen?
Version 3.0.13 doesn’t include any keybinding changes, so something is most likely intercepting those shortcuts. The log from step 2 should show exactly what.
As you can see in the attached video, I have uninstalled all my extensions, and the log seems to be detecting the shortcut just fine. However, the window seems to not be responding to it. I have also attached the log here for your reference.
I still think it has something to do with Cursor newer version. The shortcuts were working just fine until this morning. And after I quit, and reopen, then the problem started.
Also to note, on the video above I have also unset all my user-defined keyboard shortcut. I put empty array in the ~/Library/Application Support/Cursor/User/keybindings.json file.
Running 3.0.13 and reporting the exact same issue.
I was using the shortcuts to move editor to next / previous split, and shortcuts to cycle through open tabs, and they seem to be correctly interpreted (see the keybindings troubleshoot) but don’t take effect on the editor itself.
I can see the second user confirmed the same issue. The team is aware of this bug with the editor-group commands in 3.0, and your reports with logs and video help us prioritize it.
As a workaround for now, try switching to Agent Layout. The editor-group commands work correctly there.
