`Terminal: Focus Next Terminal Group` doesn't work via default keybindings

Support Bug Reports
3

Hey, thanks for the report and for finding a fix with terminalFocusInAny.

This is a known issue. Cursor sometimes sets context variables like terminalHasBeenCreated and terminalProcessSupported incorrectly, so the when conditions for the default keybindings don’t trigger. The team is working on a fix.

Your solution is correct. As a temporary workaround, you can add explicit bindings in keybindings.json:

{
  "key": "cmd+shift+]",
  "command": "workbench.action.terminal.focusNext",
  "when": "terminalFocusInAny && terminalHasBeenCreated && !terminalEditorFocus || terminalFocusInAny && terminalProcessSupported && !terminalEditorFocus"
},
{
  "key": "cmd+shift+[",
  "command": "workbench.action.terminal.focusPrevious",
  "when": "terminalFocusInAny && terminalHasBeenCreated && !terminalEditorFocus || terminalFocusInAny && terminalProcessSupported && !terminalEditorFocus"
}

Related cases: CMD+SHIFT+[ doesn't toggle terminals

1 Like