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

Last updated: July 13, 2026

Available on: Mac

If Flow's keyboard shortcuts (like fn+space or Escape) suddenly stop working while hold-to-talk still works fine, another app on your Mac is likely blocking them via Secure Event Input. This guide helps you identify the culprit and get your shortcuts working again — most cases resolve in under a minute.

Quick checks

  • Is a password field focused? Click into any non-password field (like a browser URL bar) and test fn+space again.

  • Is Terminal open? Terminal's Secure Keyboard Entry setting can block Flow even when Terminal is in the background.

  • 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? at the end of this article.

How to fix it

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

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

  2. Check Terminal's setting. Open Terminal, click the Terminal menu in the menu bar, and make sure Secure Keyboard Entry is unchecked. Test fn+space — if it works, you're done.

  3. Quit the offending app entirely with Cmd+Q (closing the window is not enough). Test fn+space — if it works, you're done.

  4. Lock your screen with Ctrl+Cmd+Q, then unlock it. This often clears a stuck system-level block faster than a full logout. Test fn+space — if it works, you're done.

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

Note: Hold-to-talk keeps working while shortcuts are blocked, so you can use it as a workaround until you clear the block.

Common triggers

Secure Event Input is commonly held by:

  • Focused password fields: in browsers, Slack, system dialogs, or password managers. macOS sometimes misidentifies which app is responsible — the actual blocker is often a background app whose password field was left focused.

  • Terminal or iTerm2: with Secure Keyboard Entry enabled. This stays active even when the app is in the background.

  • Wispr Flow itself (rare): if a password field inside a Flow window (for example, during sign-in) was focused and the window was closed without clicking away first. Restarting Flow may not clear this — a screen lock and unlock will.

  • Lock screen edge cases: where an app held secure input across a lock/unlock cycle.

FAQs

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

Hold-to-talk uses a different input method that isn't affected by Secure Event Input. Keyboard shortcuts require Flow to read your keystrokes, which macOS blocks when another app has Secure Event Input active.

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

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

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

Terminal's Secure Keyboard Entry setting stays active even when Terminal is in the background. Open Terminal, click the Terminal menu, and uncheck Secure Keyboard Entry. Leaving it off prevents this from recurring.

Will this affect Flow on Windows or mobile?

No. Secure Event Input is a macOS-only feature. This issue does not apply to Wispr Flow on Windows, iOS, or Android.

Limitations and notes

  • This issue is specific to macOS. Secure Event Input does not exist on Windows, iOS, or Android.

  • Hold-to-talk continues to work while shortcuts are blocked and can be used as a workaround.

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

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 (this indicates a different problem).

Include your macOS version, the apps you had open when shortcuts stopped working, and the steps you've already tried. Most Mac shortcut issues are resolved in one reply.