Context Awareness

Last updated: April 30, 2026

Available on: Mac, Windows, Android (Windows support is more limited)

Context Awareness reads your active app and adapts transcription accuracy, style, and formatting automatically — so emails sound like emails and Slack messages sound like Slack messages.


What it is

Context Awareness identifies the application you're using and adjusts your dictation accordingly. It improves accuracy by detecting names in emails, applies your Style Personalization settings based on the app category, and handles smart formatting in apps like Notion.

Context Awareness is enabled by default.


When to use it

Use this feature when you want to:

  • Dictate emails and have Flow automatically recognize recipient names and apply a professional tone.

  • Switch between apps like Slack and Google Docs without manually adjusting your writing style.

  • Dictate into Notion without Flow picking up placeholder text like "Heading 1" or "Type something..."


How it works in Flow

Overview

Flow reads limited text near your cursor and identifies your active app — using accessibility APIs on Mac, UI Automation on Windows, and app detection on Android. For browser-based apps, Flow identifies the specific website by URL, so Gmail, Google Docs, and other web apps are recognized individually.

Flow recognizes four app categories — Email, Work messaging, Personal messaging, and Other — each with different default writing styles. Personal messaging defaults to Casual and uniquely offers a Very Casual option, while Email, Work messaging, and Other default to Formal.

Key behaviors

  • Improved accuracy: Flow uses names and context visible on screen (such as email recipients) to recognize proper nouns and preserve correct capitalization.

  • Style matching: Flow detects your active app's category and applies the matching Style Personalization settings you configured during onboarding. On Android, style changes take effect immediately — even if you start dictating right after switching styles.

  • Conversation context: Flow reads conversation context in Slack and Apple Messages for better transcription accuracy. Other apps benefit from general nearby-text reading but do not have dedicated conversation context support.

  • Smart formatting in Notion: Flow detects and ignores common placeholder text in Notion fields (such as "To-do", "Heading 1", and "Type something..."), so dictated text appears in the right place with correct formatting.

  • Browser recognition: Chrome, Safari, Arc, Brave, Edge, Firefox, Opera, and other browsers are supported. Flow identifies the specific website rather than the browser. On Android, web apps in browsers (such as Gmail, Slack, or WhatsApp Web in Chrome) are recognized individually.

  • Android app coverage: Flow recognizes a wide range of popular Android apps and automatically applies the right writing style for each category. This includes personal messaging apps (WhatsApp, Telegram, Signal, Messenger, Discord, and more), work apps (Slack, Teams, Zoom, LinkedIn, Notion, Jira, Google Docs, and more), and email clients (Gmail, Outlook, ProtonMail, Spark Mail, and OEM mail apps from Samsung, Xiaomi, Oppo, and others).

  • Context-aware formatting: Flow adjusts casing, spacing, and punctuation based on surrounding text. When continuing mid-sentence, the first letter is lowercased. Leading and trailing spaces are added as needed. In messaging apps, trailing periods are stripped for a more casual tone (controlled by your writing style setting).

  • Persistent context: Flow remembers file names from Cursor and channel or user names from Slack across dictation sessions, so proper nouns seen in one session are recognized in the next.

Privacy protections

  • Local processing: Context data is read locally on your device. During an active dictation session, relevant context (such as nearby text and proper nouns) is sent to Wispr's servers to improve transcription accuracy, but it is not retained after the session completes.

  • Password fields excluded: Password field contents are never read or included in context data. Your spoken audio is still processed for transcription as normal. On Mac, password field detection relies on the standard macOS secure text field indicator — some custom or non-standard password inputs may not be detected.

  • Privacy Mode: When enabled, no dictation or context data is retained or used for training. Privacy Mode is permanently locked on if you have signed the HIPAA Business Associate Agreement (BAA) or if your organization enforces zero data retention (ZDR).

  • Accessibility permissions: On Mac, you must grant accessibility permissions in System Settings for Context Awareness to function. On Windows, no explicit accessibility permissions are required.

Note: To disable Context Awareness for sensitive environments (legal, healthcare, or regulated data), go to SettingsData and Privacy.

Warning: Signing the HIPAA BAA is irreversible. You will be asked to type your legal name to confirm, and Privacy Mode is permanently locked on. Enterprise users manage the BAA through their admin portal.


Examples

Dictating an email in Gmail

What happens: Flow detects you're composing an email, reads the recipient's name, and applies your email writing style from Style Personalization.

You say: "hey sarah thanks for sending over the proposal i'll review it by friday"

Flow types: Hey Sarah, thanks for sending over the proposal. I'll review it by Friday.

Switching from email to Slack

What happens: Flow detects you've moved to a work messaging app and switches to your casual messaging style — no manual adjustment needed.

You say: "sounds good let's sync tomorrow morning"

Flow types: sounds good, let's sync tomorrow morning

Dictating into a Notion page

What happens: Flow ignores Notion's placeholder text ("Heading 1", "Type something...") and inserts your dictated text cleanly into the correct field.

You say: "project kickoff next tuesday at ten am"

Flow types: Project kickoff next Tuesday at 10am.


FAQs

Does Context Awareness work with Style Personalization?

Yes. Flow detects your active app's category and applies the matching writing style you configured during onboarding. On Android, this works across all supported apps — including web apps in browsers — and style changes take effect on your very next dictation.

How do I turn off Context Awareness?

Open Wispr Flow, go to SettingsData and Privacy, and toggle off Context awareness.

If your organization has disabled Context Awareness for all users, the toggle is off and locked. Hovering over it shows the tooltip "This setting is managed by your organization."

Is Context Awareness HIPAA compliant?

Context Awareness is compatible with HIPAA workflows. Sign the Business Associate Agreement (BAA) in SettingsData and Privacy to permanently lock Privacy Mode on. Context Awareness can also be independently disabled for additional caution.

Can enterprise admins control Context Awareness for their organization?

Yes, on Enterprise plans. Admins go to the Organization settings page and find Context Awareness under Data Controls. They can set it to Available (the default — each user controls their own toggle) or Disable for all users (turns Context Awareness off for everyone and locks the toggle).

Admins on Team or lower-tier plans see the setting as disabled with an "Enterprise only" tag.


Limitations and notes

  • Context Awareness is available on Mac, Windows, and Android. Windows support is more limited — some accessibility tree features available on Mac may not function identically, and context-aware formatting adjustments are skipped when dictating inside the Flow app itself.

  • On Mac, accessibility permissions must be granted in System Settings for Context Awareness to function.

  • On Enterprise plans, admins can disable Context Awareness for all users from the Organization settings page under Data Controls. Enterprise organizations can also enforce local data deletion policies (auto-delete after 24 hours, or never store) separately from ZDR.

  • Context reading has built-in performance limits: a 0.75-second timeout for the accessibility tree scan and a 150,000-character cap. In code editors like Cursor and VS Code, additional context (file names, text areas) is collected with a 1-second timeout.