Keyboard shortcut does not work on macOS: System-wide hotkey captured by third-party application

Problem

A keyboard shortcut configured in a JetBrains IDE does not trigger the bound action on macOS, while other shortcuts work correctly. For example, Ctrl+Opt+Shift+Up (Previous change) has no effect, while Ctrl+Opt+Shift+Down (Next change) works as expected.

Cause

A third-party application has registered the same key combination as a system-wide hotkey. On macOS, system-wide hotkeys are intercepted by the registering application before the keystroke reaches the focused window, so the IDE never receives the input.

Common culprits include:

• Window managers (for example, Rectangle, Magnet, Spectacle, Amphetamine)
• Screenshot and screen recording tools
• Input source switchers
• Clipboard managers

Resolution

Use one of the following options.

Option 1: Reassign or disable the shortcut in the third-party application

1. Identify which application has registered the conflicting hotkey. In System Settings | Keyboard | Keyboard Shortcuts, review App Shortcuts and Services. For shortcuts registered outside the macOS keyboard panel, check each running utility's own preferences.
2. In the conflicting application, either disable the shortcut or rebind it to a different combination.

For Rectangle specifically:

1. Open Rectangle | Preferences.
2. Locate the action bound to the conflicting combination.
3. Change or clear the shortcut.

Option 2: Assign a different shortcut in the IDE

1. Open Settings | Keymap.
2. Locate the action — for example, Main menu | Navigate | Navigate in file | Change Navigation Actions | Previous change.
3. Right-click the action and select Add Keyboard Shortcut.
4. Assign a combination that does not conflict with system or third-party shortcuts.

For details, see Configure keyboard shortcuts.

Verification

To confirm a shortcut conflict before changing settings:

1. Quit any third-party utility that may have registered global hotkeys (window managers, input switchers, screenshot tools).
2. Test the shortcut in the IDE.
3. If the action triggers correctly with the third-party app closed, the conflict is confirmed.