Fix Flow shortcuts blocked by macOS Secure Keyboard Entry / Secure Event Input

Last updated: September 1, 2026

Available on: Mac

If fn+space or Escape suddenly stop working while hold-to-talk still works, another app on your Mac is holding Secure Event Input. Identify the culprit and clear it — most cases resolve in under a minute.

Quick checks

  • Is a password field focused? Click into any non-password field, such as a browser URL bar, and test fn+space again.

  • Did Flow just launch, or did your Mac just wake or unlock? Shortcuts can pause for a few seconds while Flow re-establishes keyboard monitoring. This recovers on its own — retry fn+space.

  • Does Flow have Accessibility permission? If shortcuts do nothing at all, check System Settings → Privacy & Security → Accessibility. Keyboard monitoring does not start without it.

  • Does hold-to-talk still work? If yes, this is a Secure Event Input issue — follow the steps below. If hold-to-talk is also broken, the problem is elsewhere — skip to Still need help?

How to fix it

Work through these steps in order. The first resolves most cases.

  1. Switch away from the app you suspect, or click into a non-password field such as a browser URL bar. Press fn+space — if Flow responds, you're done.

  2. Open Terminal, click the Terminal menu in the menu bar, and uncheck Secure Keyboard Entry. Test fn+space — if it works, you're done.

  3. Close the suspected app's window, starting with password managers such as 1Password. Test fn+space, then quit the app with Cmd+Q if it's still blocked.

  4. Lock your screen (Ctrl+Cmd+Q) and unlock it, which can clear a lingering block. Test fn+space.

  5. Log out of macOS from the Apple menu → Log Out, then sign back in and test fn+space. If shortcuts still fail, contact support.

Tip: Use hold-to-talk until the block clears, or double-press Fn for hands-free dictation — modifier keys keep working while regular key presses are blocked. If Fn isn't available on your keyboard, the backup Mac shortcuts are Ctrl+Opt (push-to-talk), Ctrl+Opt+Space (hands-free), and Cmd+Ctrl+Opt (Command Mode).

Note: Quitting and reopening Wispr Flow will not clear the block — macOS holds it, not Flow.

Common triggers

  • Password managers (e.g. 1Password): a focused password field in a password manager window is one of the most common causes. Closing that window usually clears the block; quitting the app may not.

  • Focused password fields: in browsers, Slack, or system dialogs — often a background app whose password field was left focused.

  • Terminal or iTerm2: with Secure Keyboard Entry enabled, which stays active in the background.

  • Wispr Flow itself (rare): a password field inside a Flow window, such as sign-in, that was focused when the window closed. Close or quit the app holding the password field, or log out and back in.

FAQs

Why does hold-to-talk still work when shortcuts don't?

macOS keeps delivering modifier-key events but blocks regular key presses, so holding Fn works while Space (hands-free dictation) and Escape (cancel dictation) stop responding. Escape is a regular key press, so the cancel command never reaches Flow.

Why doesn't Flow alert me the moment shortcuts stop working?

Brief password-field focus is normal and momentary, so an alert would fire too often to be useful. You'll notice because keyboard shortcuts stop while hold-to-talk keeps working.

Terminal keeps blocking Flow even after I switch windows — why?

Terminal's Secure Keyboard Entry stays active in the background. Uncheck it as described in How to fix it, and leave it off to prevent this recurring.

Will this affect Flow on Windows or mobile?

No. Secure Event Input is macOS-only, so this does not apply to Wispr Flow on Windows, iOS, or Android.

Limitations and notes

  • macOS does not always accurately identify which app is holding Secure Event Input, so you may need to try more than one suspected app.

  • Shortcuts may not respond for a few seconds after Flow launches or after your Mac wakes or unlocks, while Flow re-establishes keyboard monitoring.

Still need help?

Reach out to our support team if:

  • Shortcuts remain blocked after quitting suspected apps and logging out and back in.

  • Shortcuts fail consistently and you cannot identify the responsible app.

  • Hold-to-talk is also broken, which indicates a different problem.

Include your macOS version, the apps open when shortcuts stopped, any app Flow reported as blocking input, how long shortcuts have been blocked, and what you've tried. Most Mac shortcut issues are resolved in one reply.