Wispr Flow in Cursor and VS Code: variable recognition, file tagging, and pasting into terminals
By Ryleigh Newman · Published
Wispr Flow has two features for code editors on Mac and Windows, which its settings group under Vibe coding. Variable recognition reads the names visible in your editor, so saying user ID can come out as userId. File tagging turns a spoken filename into an @ tag in an AI chat panel. Both have conditions that are easy to miss, and the first one depends on a setting inside the editor, not inside Flow.
I built YapToText, a different dictation app for the Mac, so read what I say about Wispr Flow with that in mind. Every fact about Wispr Flow here comes from its own help center, read on October 10, 2026.
This app is completely free. You don't have to make an account. There are no subscriptions, no difficult downloads, and nothing is locked. Made for Apple silicon Macs. Source on GitHub.
This guide in other languages: العربية, Čeština, Dansk, Deutsch, Ελληνικά, Español, Suomi, Français, עברית, हिन्दी, Magyar, Bahasa Indonesia, Italiano, 日本語, 한국어, Norsk, Nederlands, Polski, Português, Română, Русский, Slovenčina, Svenska, ไทย, Türkçe, Українська, Tiếng Việt, 简体中文, 繁體中文
On this page: 8 sections
What works where
From Wispr Flow's help article Use Flow with Cursor, VS Code, and other IDEs, read October 10, 2026. On a Mac, Flow needs Accessibility permission to read the editor.
| Feature | Where it works |
|---|---|
| Variable recognition | Cursor and standard VS Code, on Mac and Windows, plus one other AI editor Wispr lists |
| File tagging | The AI chat panel in Cursor, and in that other editor. Not in VS Code |
| Neither | VS Code Insiders |
Turning on variable recognition
- In Flow, open Settings, Vibe coding, and choose Set up beside Variable recognition for the instructions.
- In the editor, open the Command Palette: Command Shift P on a Mac, Control Shift P on Windows.
- Run Toggle Screen Reader Accessibility Mode. Running it again turns it off.
- Check that Screen Reader Optimized shows in the editor's status bar.
- Keep the file open and dictate a phrase with a visible variable or function name.
There is no switch for it in Flow: it works only while the editor is in Screen Reader Optimized mode. Names that are off screen, placeholder text and very large files can be skipped, and a heavily customized editor can stop Flow from detecting the mode. The help center says recognition may be weaker on Windows.
Tagging files by voice
- Open the file in a tab, or make it visible in the sidebar.
- Click the AI chat input that supports @ autocomplete.
- Say the full filename with its extension, or say tag, at, or @ before its base name.
- Examples from the help center. Check index dot ts for errors tags
index.ts. Explain this code, tag my python script tagsmy_python_script.py. - Names need a dot. A filename without a dot cannot be tagged. For
.env, say dot before the name. - Dictionary entries switch it off. Any dictionary or snippet substitution in a dictation turns tagging off for that whole dictation.
- No match, no change. If nothing matches, the dictation is pasted unchanged, trigger word included.
- Not in terminals. Flow skips tagging in what it recognizes as a terminal.
Pasting into the editor and its terminal
Click the field, hold the shortcut (Fn on a Mac, Control Windows on Windows), speak, let go, and wait for the whole paste before you type. On Windows, in supported editors and their built-in terminals, Flow pastes with Shift Insert instead of Control V, and that cannot be changed. If text goes missing, use Paste last transcript, Command Control V on a Mac or Shift Alt Z on Windows, or copy it and use the terminal's own paste, which in some terminals is Control Shift V. The Wispr Flow not pasting page covers the rest.
If recognition or tagging does not work
- Check the conditions. The right editor, Accessibility on a Mac, Screen Reader Optimized for variables, the file visible, the chat input for tags.
- Close unused tabs. The help center suggests it if reading the editor feels slow.
- Restart both. Quit and reopen Flow and the editor, then dictate a visible name again.
Coding with YapToText instead
Wispr Flow from its help center, read October 10, 2026. YapToText from its own settings.
| Wispr Flow | YapToText | |
|---|---|---|
| Reads names in your editor | Variable recognition, with Screen Reader Optimized mode | No. Teach names with a dictionary instead |
| Tags files in an AI chat | Yes, in Cursor and one other editor | No |
| Formatting for code | Not covered in this article | Auto mode leans Code Comment in VS Code, Cursor, Xcode and other editors |
| Terminals | Pastes, skips tagging | Insert adjustments are off automatically in Terminal, iTerm2, Warp, Ghostty and others |
| Internet | Needed | Not needed |
A YapToText dictionary is the closer tool for code names: it turns swift ui into SwiftUI every time, and its words also prime the speech model. Wispr's two editor features have no equivalent in YapToText. Dictation in Cursor, dictation in VS Code and dictation for coding cover each editor.
This app is completely free. You don't have to make an account. There are no subscriptions, no difficult downloads, and nothing is locked. Made for Apple silicon Macs. Source on GitHub.
The short version
- Variables. Turn on Screen Reader Optimized mode in the editor.
- File tags. Say the filename with its extension in the AI chat panel.
- Not in VS Code. File tagging works in Cursor, not VS Code.
- Windows paste. Shift Insert in editors, Shift Alt Z for the last transcript.
- Dictionary entries. They turn tagging off for that dictation.
If Wispr changes these features, open an issue on GitHub and I will update this page. Every one gets read.
This app is completely free. You don't have to make an account. There are no subscriptions, no difficult downloads, and nothing is locked. Made for Apple silicon Macs. Source on GitHub.
Related
Sources
- https://docs.wisprflow.ai/articles/6434410694-use-flow-with-cursor-vs-code-and-other-ides (checked 2026-10-10)
- https://github.com/ryleighnewman/YapToText (checked 2026-10-10)
- https://apps.apple.com/us/app/yaptotext/id6786382289 (checked 2026-10-10)
Questions
Does Wispr Flow work in Cursor?
Yes, on Mac and Windows. Cursor supports both variable recognition and file tagging in its AI chat panel.
Why does Wispr Flow not recognize my variable names?
Variable recognition only works while the editor is in Screen Reader Optimized mode. Run Toggle Screen Reader Accessibility Mode from the Command Palette.
Can Wispr Flow tag files in VS Code?
No. Its help center says standard VS Code supports variable recognition but not file tagging.
How do I tag a file with Wispr Flow?
In Cursor's AI chat input, say the full filename with its extension, or say tag before its base name. The file must be open or visible.
Why does Wispr Flow use Shift Insert to paste in VS Code on Windows?
In supported editors on Windows Flow pastes with Shift Insert instead of Control V, and there is no setting to change it.