Hey, this is a known issue. On Windows, Ctrl+1 Focus First Editor Group stops working when chat-editor-group mode is active, while Ctrl+2 to Ctrl+8 still work, so it looks like it only works one way. Reloading temporarily removes the block, but it comes back later.
A working workaround is to remove the when condition from this keybinding:
Open Keyboard Shortcuts
Find View: Focus First Editor Group
Right click the binding, then Change When Expression, then delete !cursor.chatEditorGroup.enabled and leave the field empty
Alternatively, you can add a rule in keybindings.json for ctrl+1 to workbench.action.focusFirstEditorGroup with an empty when.
We’ve logged this bug on our side. There’s no exact timeline for a fix yet. Let me know if the workaround didn’t help.
Rechecked on 3.23.13: Ctrl+1 or Cmd+1 is still unbound whenever the chat is shown as an editor group in the unified layout. Ctrl+2 and Ctrl+3 still work. That’s why it feels one way, and why reloading sometimes fixes it for a bit. I’ve passed this to the team again, but it isn’t being actively worked on right now and I don’t have an ETA.
Workaround for now: in Keyboard Shortcuts, add your own binding for workbench.action.focusFirstEditorGroup with no when clause. I’ll post here if anything changes.