A shortcut conflict exists when two active layers claim the same key combination or when one layer intercepts it before the intended window command receives it. Diagnose ownership before inventing a more complicated chord.
Make a shortcut ownership table
Record the key, expected action, and every possible owner:
| Layer | Places to check |
|---|---|
| macOS | Keyboard Shortcuts, Mission Control, App Shortcuts |
| Front app | application preferences and menu equivalents |
| Window utility | global hotkey settings |
| Launcher or automation tool | extensions, scripts, keyboard remappers |
Raycast can warn when a recorded hotkey conflicts with another command inside Raycast. Other conflicts still require checking the system and peer apps.
Reproduce with one owner
Choose a harmless test window. Disable one conflicting assignment, not the entire set of utilities, then invoke the shortcut from the same front app and Space. Record whether the expected UI appears. Repeat only if the result remains ambiguous.
Also check input sources, because a punctuation key may map to another character. Accessibility permission can affect a utility’s ability to complete a window action, but missing permission is different from another command firing.
Resolve and preserve a fallback
Give the shortcut one primary owner. Remove the duplicate or select a chord that does not shadow a common application command. Keep Mission Control, a menu command, or the Dock as a fallback while testing.
Do not reset every keyboard preference at once; that destroys evidence and can create new conflicts. A stable configuration has a small documented set of global shortcuts whose scope and owner are clear.