Voice dictation in Claude Code and the terminal
A good prompt for Claude Code is often a whole paragraph about what's broken and what you already tried. That's quicker to say than to type. Terminals are also where dictation tools fail most often, so here's what goes wrong on a Mac and what has worked for us.
Where dictation goes wrong in a terminal
A terminal window isn't a normal text field. Claude Code draws its own prompt inside the terminal and reads whatever the terminal passes to it. Dictation tools on macOS are mostly built around text fields they can inspect through the Accessibility API. A lot of the trouble comes from that mismatch.
The complaints we've seen on Reddit and the Cursor forum fall into a few groups.
- Text arrives in pieces. Cursor users have reported stray periods in the middle of sentences from its built-in dictation, and a Cursor forum thread from early October describes dictation into the Cursor CLI cutting off. Streaming tools commit words before you've finished the sentence, which is a likely explanation. We haven't seen the code behind either one, so treat that as a guess.
- Text never arrives. In an r/ClaudeCode thread, someone dictating into Claude Code inside VS Code's integrated terminal said the text simply wasn't inserted. Some tools type by sending synthetic keystrokes and others paste through the clipboard. When one method fails in a terminal, a tool that uses the other one is worth trying.
- Nobody notices the failure. VS Code and Cursor are Electron apps, and Electron keeps its text fields hidden from the Accessibility API until an assistive app asks for them. A tool that can't see the field can't check whether the text landed, so a failed paste looks exactly like a successful one.
What works
Two habits fix most of it. Let the tool finish the whole take before anything goes into the terminal, and have it insert the text once. One paste is what you already do with ⌘V all day, and every terminal handles it. If your tool can only stream, dictate into a scratch note and paste from there.
Then read the prompt before you press Enter. Dictation will sometimes mishear an identifier, and an agent will act on the wrong file name without complaint.
Claude Code's built-in /voice
Claude Code has its own dictation. Run /voice, hold Space and talk. Your words show up in the prompt as you speak, and the final transcript is inserted at the cursor when you let go. By default it then waits for Enter. Anthropic says it's tuned for coding vocabulary and adds your project name and git branch as recognition hints. If you're signed in with a Claude.ai account and fine with cloud transcription, it's the shortest path.
The documentation is clear about the limits. Audio is streamed to Anthropic's servers and isn't processed locally. It doesn't work when Claude Code runs on an API key, Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry, or in SSH and cloud sessions. Hold mode watches for key-repeat events from your terminal, so recording starts after a short warmup. And it only covers Claude Code's own prompt.
How FnFlow handles it
FnFlow sits outside the terminal. You hold fn (or right ⌘), talk and let go. While the key is down it only records. Whisper transcribes the whole take on your Mac after release, and the text goes in with a single ⌘V. Your clipboard comes back afterwards unless you copied something new in the meantime.
After pasting, FnFlow tries to read the field back. When it can, the pill says Pasted. When the app doesn't expose the field, it says Paste sent, which means the command went out but wasn't confirmed. If the paste couldn't happen at all, for example because you switched windows, the pill says Saved · ⌘V and the text waits in history next to its audio. In Electron apps like VS Code and Cursor, FnFlow first sets Electron's documented AXManualAccessibility attribute so their fields become visible.
Because the text is pasted into the terminal window, FnFlow doesn't care what's running inside it or which account Claude Code uses. A shell on a remote machine just receives the pasted text. We test mostly in Cursor and the Claude app, so if a terminal misbehaves, the history is your fallback.
A setup that works
- Add your project names to Settings → Vocabulary, for example "Supabase, Postgres, pgvector". Whisper uses up to 60 of them as spelling hints.
- Click into the Claude Code prompt.
- Hold fn and describe the task. For a long one, double-tap fn to go hands-free.
- Let go, read the prompt, fix any misheard name and press Enter.
Questions
Does Claude Code have built-in voice input?
Yes. Run /voice, then hold Space and talk. According to Anthropic's docs, the audio is streamed to Anthropic's servers for transcription, and the feature needs a Claude.ai sign-in. It isn't available with an API key, Bedrock, Google Cloud's Agent Platform or Microsoft Foundry, or in SSH and cloud sessions.
Can I use FnFlow and /voice at the same time?
Yes. Claude Code's /voice uses Space by default and FnFlow uses fn or right ⌘, so the keys don't collide. FnFlow just pastes text into the terminal window, and Claude Code sees it as a regular paste.
Why does dictated text sometimes not show up in the VS Code terminal?
We don't know the exact cause for every tool. VS Code is an Electron app, which hides its fields from the Accessibility API until an assistive app asks for them, and tools insert text in different ways. A tool that transcribes first and pastes once is the safest bet, and it helps if the tool tells you when the paste wasn't confirmed.
Does FnFlow send my prompts anywhere?
No. Recognition runs on your Mac. The prompt goes wherever Claude Code sends it once you press Enter.
Local Wispr Flow alternativeFnFlow vs VoiceInkVoice input for CursorHow 7 Mac dictation apps get you to your first dictationWhisper.cpp on Apple Silicon: which large-v3-turbo quantization to shipHow I built a local dictation appWhy holding fn doesn't work for dictation on Mac (and how to fix it)How to run Whisper locally on an Apple Silicon MacSpokenly alternative for developersFnFlow vs EnviousWisprHow to dictate a good prompt for AI coding toolsVoice dictation in VS Code on a MacTeaching Whisper your jargon: initial prompt and replacementsWhy Whisper types "Thank you" on silence, and how to filter itPrivate dictation on a Mac at work: what actually leaves your machineVoice input for Codex CLI and the ChatGPT appVoice coding on a Mac: what actually worksWriting git commit messages by voiceDictating code review comments on GitHubDictation in IntelliJ IDEA, PyCharm and WebStorm on a MacDictation in Zed on a MacDictation in Terminal, iTerm2 and WarpWhich Whisper model to use on an Apple Silicon MacPush-to-talk dictation on a Mac: hold, toggle or streamSuperwhisper alternative for developersClaude Code voice mode: how to enable /voice and fix itWhisper apps: five ways to run Whisper locallyTalon voice coding vs a dictation appPush to talk on a MacDoes Claude have a voice mode?VoiceInk vs Wispr FlowVoiceInk vs SuperwhisperParakeet vs Whisper on a MacApple SpeechAnalyzer vs WhisperWhisper.cpp vs faster-whisper on a MacMlx-whisper vs whisper.cppGitHub Copilot voice inputGemini CLI voice inputVoice input in Google AntigravityVibe coding with voice input