# Understand shortcut scope and conflicts

A shortcut can be global, specific to the current screen or handled by the focused application. Diagnose its scope before changing permissions or bindings.

## Identify what receives the key

| Situation | First check |
| --- | --- |
| Ouros is closed | Open Ouros X from Applications. |
| The app menu works but the global control does not | Check Input Monitoring and the current assignment. |
| Arrows move a caret instead of a result | Focus the result list rather than the editor. |
| A terminal receives letters or Control C | The shell or foreground process owns terminal input. |
| Escape returns to a smaller view | A nested layer handled the first dismissal. |

A solo Right Option tap differs from Right Option held with a letter. The same distinction applies to other modifier taps. Release other keys before testing a solo tap.

## Check a binding conflict

Open Settings → Shortcuts and inspect the chosen action and saved chord. The editor reports unavailable or conflicting assignments. Saved user bindings have priority over factory defaults; clearing a saved chord can leave an available factory chord active.

Test the chord once from a plain application and once from the screen where it failed. Record which app had focus, your keyboard layout and the exact action that occurred.

## Check keyboard utilities

A remapper or another application's global shortcut may receive the chord first. Inspect the affected mapping instead of disabling every utility or resetting system access. See [custom shortcuts and layouts](/docs/keyboard/custom-shortcuts-and-layouts).