Fix Pluely v1 Global Keyboard Shortcuts Not Working

Pluely v1 relies on global keyboard shortcuts to toggle the overlay, trigger push-to-talk, and control Listen mode from anywhere on your desktop. When a shortcut stops responding, it's almost always one of three causes: a missing system permission, a conflict with another app claiming the same key combination, or a shortcut that never registered correctly in the first place.

1. Grant Accessibility permission (macOS)

Global shortcuts on macOS require Accessibility permission, since the OS treats system-wide key monitoring as a sensitive capability.

1. Open System Settings > Privacy & Security > Accessibility.
2. Confirm Pluely is listed and its toggle is on. If it's missing, try using a shortcut once to trigger the prompt, or add Pluely manually via the "+" button.
3. Quit Pluely completely and reopen it — Accessibility permission changes typically don't take effect until the app restarts.
4. Test your shortcuts again.

See Permissions for the full list of permissions Pluely v1 uses and why each is needed.

2. Check for a conflict with another app

If another application already claims the same key combination, your OS or that app may swallow the key press before Pluely ever sees it. Common conflicts come from:

• Window managers or tiling tools that bind system-wide hotkeys.
• Other always-on-top utilities, launchers, or clipboard managers.
• Media keys or OS-level shortcuts (screenshot tools, Spotlight/search, virtual desktop switching).

1. Temporarily quit or disable other hotkey-based utilities one at a time.
2. Retest Pluely's shortcut after each one.
3. Once you find the conflicting app, either change that app's shortcut or change Pluely's to a combination nothing else uses.

3. Re-set the shortcut inside Pluely

Sometimes a shortcut binding simply doesn't save correctly, especially after an update or a settings import.

1. Open Settings inside Pluely and go to the shortcuts/keybindings section.
2. Click into the shortcut field that isn't working.
3. Press a new key combination (even if it's the same one you intended before) so it re-registers cleanly.
4. Confirm the change is saved, then test immediately.

If you use unusual modifier combinations (e.g., involving Fn or media keys), try a simpler combination first to rule out OS-specific quirks with that key.

4. Restart Pluely after any change

Shortcut registration happens at startup on most platforms. After granting a permission, resolving a conflict, or re-setting a binding, fully quit and relaunch Pluely rather than assuming it will pick up the change live.

5. Windows and Linux specifics

• Windows: some shortcuts (especially combinations already used by Windows itself, like certain Win+key combos) may be silently intercepted by the OS. Try an alternate combination if a specific key seems dead everywhere.
• Linux: desktop environments (GNOME, KDE, etc.) often have their own global shortcut layer that can take priority. Check your desktop environment's keyboard shortcut settings for a conflicting binding.

Still stuck?

If shortcuts still don't respond after granting Accessibility (macOS), checking for conflicts, and re-setting the binding, check the FAQ or reach out from the Pluely website with your OS and the exact key combination affected.