Keyboard shortcut does not work since upgrading to 3.0.13

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

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

Operating System

MacOS

Version Information

Version: 3.0.13
VSCode Version: 1.105.1
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. A couple quick questions so we can figure out what’s causing it:

  1. 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?

  2. 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.

  3. 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.

Let me know what you find.

Hi @deanrie

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.

keyboard-troubleshoot.txt (9.4 KB)

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.

Hello :waving_hand:

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.

Please find attached video.

Thanks for the video and logs.

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.

Let me know if that helps.

Don’ know if it helps, but In Agent mode I have nextEditor working but not moveEditorToNextGroup.

Thanks you :folded_hands:t2:

Hi @deanrie is there any update for this? I tried to upgrade to 3.0.16 but the issue persists.

Is the MacOS version affecting the issue too? I am still on Sequoia 15.5

same issue, I’ve got 3.0.16 installed, it is annoying af :persevering_face:

got 3.1.10 installed, it doesn’t work still

Same here, still does not work on 3.1.10

3.1.10 installed, same behavior :pensive_face:

The bug is still being worked on, and unfortunately it’s not fixed in 3.1.10 yet. I’ve added your updates to the report for the team, it helps with prioritization.

For now, the only workaround is to use Agent Layout instead of Editor Layout. In Agent Layout, the editor-group commands work correctly, as @Gregoire_Vallette confirmed above.

@vicodinvic1, you mentioned it worked at first on 3.1.10 and then stopped. Can you clarify if that happened after restarting Cursor, or within the same session?

I’ll let you know when there’s a fix.

Yeah, it was working fine once I have updated to the latest version, but then the same issue appeared, like after 5-10 minutes of active coding and using shortcuts.
I don’t really know why and after what exact event is has broken again, tbh.

I may notice as well that sometimes it happens that it is working for a couple of times and then it doesn’t again. But it happens very very rare, so most of the time ‘move the file to the next group’ and ‘move the file to the prev group’ shortcuts just do not work for me.

Agent Layout approach you have mentioned doesn’t work for me as well. It doesn’t split editor UI into 2 panes as it does in Editor Layout mode. So it doesn’t do the same at all. ‘move the file to the next group’ shorcut does nothing in Agent Layout for me. ‘move the file to the prev group’ was working several times until it stopped to.

I’m so sorry to say, guys, but there’s overall awful UI behaviour during last month or so.
I have even started to think about switching to some other code editor because of that.
Because it is very annoying to work in such broken/unresponsive editor.

:waving_hand:t2: Just pointing out that I experience the same behavior in 3.1.14.

@vicodinvic1, thanks for clarifying. The fact that shortcuts work for the first 5 to 10 minutes and then stop is a really helpful detail for debugging.

About Agent Layout, it works differently from Editor Layout and doesn’t support split editor in the usual way. So unfortunately there isn’t a full workaround right now.

The bug is logged and the team is aware. I don’t have an exact timeline for a fix yet, but your reports help us prioritize. I’ll update the thread when there’s news.

Hello.

I’m puzzled about the delay thing.

Straight when opening cursor, and two tabs, trying moveEditorToNextGroup doesn’t split the editor like it used to. I’ve never experienced such a behavior change depending on the time since startup.

can confirm it does work for me on 3.1.15 so far

Experiencing the same issue.
This bug is frustrating for engineers and needs to be FIXED.
I’m on 3.1.15, and still NOT BE FIXED!!!