Keyboard shortcut does not work since upgrading to 3.0.13

Support Bug Reports
, ,
26

@Surtin, @Gregoire_Vallette, this is a known bug and the team is aware. Sadly, it’s not fixed yet.

Can you share your full Cursor version from Help > About, and which layout you’re using, Editor or Agent? That’ll help with debugging.

@vicodinvic1, glad it’s still working on 3.1.15 for now. Let me know if it breaks again, I’m especially interested in how long after launch it happens.

27

Looks fixed in 3.1.15 from what I’ve seen so far ! Will let the others confirm, thank you team :clap:t2:

28

3.1.15 seems to fix most of the issues. I still have some keyboard shortcuts not working, but let me double check them on my side too.

Will post a screen record later if I can confirm the issue

Thanks

29

Hi I’m experiencing the same issue as this post on 3.1.15

  • triggering workbench.action.previousEditor while on the first file tab doesn’t loop back to the first.
  • triggering workbench.action.nextEditor while on the last file tab doesn’t loop to the last tab.

I’ve tried closing/reopening cursor but the issue persists. please let me know if i can provide anything else that would help!

Version string from Help > About > Copy


Version: 3.1.15
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
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 25.4.0

What are the affected shortcut(s) and which command(s) it’s mapped to (nextEditor, nextEditorInGroup, etc)

  • alt+cmd+left → workbench.action.previousEditor
  • alt+cmd+right → workbench.action.nextEditor

Are you using Editor Layout or Agent Layout?

Editor Layout

30

Hey @nullbitme, this is a separate bug from what was discussed earlier in the thread. The wrap-around issue where nextEditor and previousEditor don’t cycle at the boundaries is already logged internally, but I can’t share an ETA for a fix yet. I’ll post an update when I have one.

Could you also check this: if you open the Agents sidebar if it’s closed, does the cycling work then? That would help confirm you’re hitting this exact case.

@DSB, you mentioned that on 3.1.15 some shortcuts still don’t work. Were you able to reproduce it? If yes, please share which ones and a screencast, and we’ll take a look separately.

31

Could you also check this: if you open the Agents sidebar if it’s closed, does the cycling work then? That would help confirm you’re hitting this exact case.

@deanrie opening the agents sidebar does resolve the issue (the agents panel tabs are now included in the cycling which i don’t personally like but that’s a separate issue)

32

@deanrie I am experiencing the same issue as @nullbitme for the cycling issue. Aside from that, the earlier bugs I reported seems to be solved.

33

Hey @DSB, glad most of the bugs are gone in 3.1.15.

Cycling at the tab boundaries is the same separate issue as @nullbitme’s. It’s logged, but there’s no ETA for a fix yet.

As a temporary workaround, try opening the Agents sidebar if it’s closed. @nullbitme confirmed above that in this case the cycling switch works, but with one caveat, the agents tabs are also included in the cycle.

If you notice any other shortcuts that don’t work on 3.1.15, please share a screencast and the list of commands, and we’ll take a separate look.