Why Wispr Flow waits to install updates while you're using it

Last updated: August 28, 2026

Available on: Mac

Wispr Flow waits until you step away before applying automatic updates, so an update won't interrupt you mid-task. If you've been active for a long stretch, Flow asks before restarting instead of doing it silently.

How it works

Key behaviors

  • Update held while you're active: you count as active when a Flow window (hub, notepad, or scratchpad) is focused and there has been keyboard or mouse input in the last few minutes. Flow re-checks once you step away.

  • Update ready dialog: after several hours of accumulated active use with an update pending, Flow shows an Update ready dialog instead of restarting. Choose Restart now to apply the update immediately, or Later to defer it until you next step away.

  • Dictation and recordings always block updates: active dictation and in-progress Notetaker meeting recordings hold the update regardless of window focus or input. Choosing Restart now re-checks for an active recording first, so a recording is never cut off.

Note: Reading a meeting summary without typing or moving your mouse counts as away, so an update may apply during that time.

FAQs

Will Flow ever restart without warning?

Only when you've stepped away — no Flow window focused and no recent keyboard or mouse input. Once you've hit the active-use threshold, Flow always shows the Update ready dialog and waits for your response.

What if I click "Restart now" during a Notetaker recording?

The restart is held until the recording finishes. Your meeting will not be cut off.

I'm managed by my IT team. Does this apply to me?

If your organization's MDM policy sets an update cadence other than automatic, updates apply on that schedule without deferral. Contact your IT administrator for your organization's policy.

Can I update immediately instead of waiting?

Yes. Click Restart now when the Update ready dialog appears.

Limitations and notes

  • This behavior is available on Mac only.

  • MDM-managed update schedules set by your IT team apply on the administrator-defined cadence and are not deferred.

  • Enterprise organizations do not currently have access to Notetaker, so Notetaker-related update blocking does not apply to them.