Cmd+Space (macOS input source switch) moves focus to terminal panel

[barnacle0q]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When the integrated terminal panel is open, pressing Cmd+Space to switch macOS input source (keyboard language) causes focus to jump from the editor to the terminal panel. Subsequent keyboard shortcuts then operate in the terminal context instead of the editor.

Steps to Reproduce

1. Open any file in the editor
2. Open the integrated terminal panel (bottom)
3. Click on the editor to ensure it has focus
4. Press Cmd+Space to switch input source (macOS language switch)
5. Focus jumps to the terminal panel

Expected Behavior

Focus should stay in the editor after switching input source.

Operating System

MacOS

Version Information

Version: 2.4.31
VSCode Version: 1.105.1
Commit: 3578107fdf149b00059ddad37048220e41681000
Date: 2026-02-08T07:42:24.999Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 24.6.0

Additional Information

• "keyboard.dispatch": "keyCode" in settings.json does not fix the issue
• The issue does not occur when the terminal panel is closed
• Also happens when a terminal editor tab (e.g. CLI tool running in editor area) is open

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report. This is a known issue: when switching the input source on macOS, focus jumps to the terminal. A few users have reported the same thing:

• Similar report (CapsLock language switch)
• Earlier thread about switching Hangul/Alphabet

It’s been happening since at least late 2025 and affects any way of changing the input source (Cmd+Space, CapsLock, Karabiner remaps, etc.).

The team is aware. Your report helps with prioritization since it confirms the issue is still present in version 2.4.31.

For now, the main workaround is to keep the terminal panel closed when you don’t need it. One user in the earlier thread also mentioned the bug sometimes went away after clearing chat history, but that seems specific to multi-model mode.

Let me know if you find any other workarounds.