In the previous version, moving left or right between active file tabs at both ends would switch files in a circuitly fashion; however, now the movement stops, making it difficult to switch files.
Het, this is a known bug that started in Cursor 3.0.x. A few keybinding editor commands like next or previous editor, split editor, move editor to group trigger in keyboard troubleshooting, but the command has no effect in the UI. It’s being discussed here: Keyboard shortcut does not work since upgrading to 3.0.13
Most of the issues were fixed in 3.1.15. A few users in that thread confirmed it. Update Cursor via Help > Check for Updates or download it from the website, then test again.
If it still happens after updating to 3.1.15 or newer, post in that thread with:
- the exact version string from Help > About > Copy
- which shortcut and which command it’s mapped to like
nextEditor,nextEditorInGroup, etc. - whether you use Editor Layout or Agent Layout
~Hey @deanrie I’m experiencing the same issue on 3.1.15~
mb sorry i’ll post up in the thread you linked.
the exact 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
which shortcut and which command it’s mapped to like
nextEditor,nextEditorInGroup, etc.
alt+cmd+left→workbench.action.previousEditoralt+cmd+right→workbench.action.nextEditor
whether you use Editor Layout or Agent Layout
Editor Layout
Hey, thanks for the detailed report @nullbitme. Looks like on 3.1.15 with the Editor Layout nextEditor/previousEditor still doesn’t cycle at the edges, I’ve logged it internally. Yep, let’s continue in this thread Keyboard shortcut does not work since upgrading to 3.0.13 since it’s already collecting context around other related regressions. If we have any updates on the fix, we’ll post them there.