File Tagging

Last updated: April 19, 2026

Available on: Mac, Windows

Tag files in Cursor and Windsurf using just your voice. Say the file name while dictating, and Flow automatically attaches it to your AI chat — no keyboard needed.

What it is

AI-powered IDEs like Cursor and Windsurf let you attach files to chats, giving the AI more context for better code suggestions. Normally you'd press @, type the file name, and select from a list. File Tagging lets you skip all that — just speak the file name and Flow handles the rest.

When to use it

Use this feature when you want to:

  • Reference files in Cursor or Windsurf AI chat without typing

  • Quickly attach multiple files while explaining a coding task

  • Stay in flow while pair-programming with AI

How it works in Flow

Overview

When you dictate in an AI chat window, Flow listens for file names and automatically tags them. File tagging is enabled by default.

Flow remembers file names from your open IDE tabs across dictation sessions, so even recently-closed files may still be matched.

When you're using a file tagging app like Cursor, Flow may suggest enabling the Cursor integration to improve your experience. This suggestion does not appear in other editors.

Key behaviors

  • Full file name: Say the complete file name with extension — "Can you fix the bug in index dot ts please?"

  • Trigger words: Say "tag," "at," "tagged," or "@" followed by the file name (extension optional) — "Can you explain this code to me, tag my python script"

  • Dot-files: For files like .env, say "dot" (or "punto" in Spanish) before the name — "dot env". Dot-files can also be tagged if the full filename appears verbatim in the transcription (e.g., ".env"). Trigger words like "tag" or "at" do not work with dot-files.

  • No-extension files: Files without an extension (no dot in the filename) cannot be tagged.

  • Smart matching: CamelCase and snake_case file names are automatically matched to naturally spoken words — say "cursor formatting" to match "cursorFormatting.ts", or "my script name" to match "my_script_name.py".

  • Ambiguous matches: When multiple files could match your spoken words, longer file names are matched first.

Note: When using a trigger word like "tag" or "at," you can say just the base file name without the extension. Without a trigger word, you need to say the full file name including the extension.

Demo

Screen Reader Mode

Cursor, Windsurf, and VS Code have a Screen Reader Mode that makes it easier for other apps to retrieve information from them. Wispr Flow uses this to better recognize variable names and file names you mention while dictating.

Key behaviors

  • Auto-enable: When "Variable recognition" is enabled, Flow automatically turns on Screen Reader Mode in your IDE after a dictation if it detects it's off.

  • Default state: Variable recognition defaults to OFF, so Screen Reader Mode is not auto-enabled until you explicitly turn it on.

  • Keyboard shortcut (Mac): Flow enables Screen Reader Mode by simulating Shift+Option+F1 in your IDE. If this shortcut is remapped or conflicts with another extension, auto-enable may not work.

  • Keyboard shortcut (Windows): The keyboard shortcut used to toggle Screen Reader Mode may differ. If auto-enable does not work, check your IDE's keyboard shortcuts for Screen Reader Mode.

  • Status detection: If Flow cannot determine the Screen Reader Mode status (e.g., the status bar indicators are not accessible), it does not attempt to toggle it.

Tip: If Flow keeps toggling Screen Reader Mode off after each dictation, make sure the Screen Reader Mode status is visible in your IDE's bottom status bar. If it's hidden, Flow cannot detect that it's already on and will send the toggle shortcut after every dictation — which turns it OFF instead of keeping it ON.

Settings

Find these options under Settings → Vibe coding:

  • Variable recognition (VS Code, Cursor, Windsurf): Controls Screen Reader Mode auto-enabling (default: OFF)

  • File Tagging in Chat (Cursor & Windsurf): Controls whether file names are auto-tagged in AI chat (default: ON)

Examples

Tagging a file by its full name

You say: "Can you fix the bug in index dot ts please?"

Flow tags: index.ts is attached to the AI chat automatically.

Using a trigger word without an extension

You say: "Can you explain this code to me, tag my python script"

Flow tags: The matching file from your open tabs (e.g., my_python_script.py) is attached.

Tagging a CamelCase file by speaking naturally

You say: "Look at cursor formatting for the styles"

Flow tags: cursorFormatting.ts is matched and attached.

FAQs

Does file tagging work in VS Code?

No. VS Code supports Variable Recognition / Screen Reader Mode, but file tagging is only available in Cursor and Windsurf.

Why did I see a Cursor integration suggestion?

Flow shows this suggestion only when you're actively using a file tagging app like Cursor IDE. It does not appear in other editors like VS Code.

Why didn't my file get tagged?

File tagging is completely disabled for any dictation where a Custom Dictionary substitution occurs. Any dictionary replacement in the transcription prevents all file tagging for that dictation.

File tagging also does not work if you're dictating in a terminal window within Cursor or Windsurf.

How do I turn off file tagging?

Open Settings → Vibe coding → File Tagging in Chat (Cursor & Windsurf) and toggle it off.

Limitations and notes

  • File tagging is available on Mac and Windows only.

  • File tagging is supported in Cursor and Windsurf — not VS Code with GitHub Copilot.

  • File tagging does not work in terminal windows within Cursor or Windsurf.

  • Files without an extension cannot be tagged.

  • File tagging is disabled for any dictation where a Custom Dictionary substitution occurs.