Can you write code by dictating it?

You can, and most people who try it end up doing something narrower: dictating comments, commit messages, documentation, pull request descriptions, and chat, then typing the code itself. Talon Voice is the exception and is built for genuine voice coding, with a real learning curve. Dictation tools that promise code by voice without that investment are overselling.

Which dictation app works in a terminal?

The requirement is verbatim output: no autocapitalization, no smart quotes, no helpful punctuation, because all three break a command. Flit switches to verbatim automatically in terminals and code editors. Most general dictation tools do not, which is why a dictated command usually arrives capitalized and unusable.

How do I dictate variable and function names?

Spoken casing commands. Say "camel case user auth service" for userAuthService or "snake case" for user_auth_service. Flit resolves these by fixed rule rather than model judgment, so they are reliable; the complete list is in the spoken command reference.

Why does dictation get my file names wrong?

Because a speech model has never seen your repository. It hears a phonetic approximation and writes the most common spelling. Flit indexes the project you have open locally, so spoken file and symbol names resolve against what actually exists in your codebase rather than against general English.

Is dictation useful if I have RSI?

Very, and it is worth separating two needs. Dictation replaces typing text; it does not replace the keyboard and mouse for controlling the computer. Talon Voice does the second, with voice, non-speech sounds, and optional eye tracking. Many people with a serious RSI run both.

The best speech-to-text for developers in 2026

Q: Does dictation work with Cursor, VS Code, and Electron apps?

It depends on how the tool inserts text. Editors built on Electron, which includes VS Code and Cursor, reject some insertion methods that work elsewhere. Flit types into every app with a cursor including Electron ones, and Voibe ships a Developer Mode aimed specifically at Cursor, VS Code, and Windsurf. Test this yourself during a trial rather than trusting a feature list.

Dictation tools ranked for the way developers actually write: terminals that must stay verbatim, symbol names that must be spelled right, and the difference between dictating prose and dictating code.

Most articles about dictation for developers start from the wrong premise, which is that the goal is writing code by voice. For a small number of people, usually those for whom the keyboard is not an option, that genuinely is the goal and there is a serious tool for it. For everyone else the honest version is narrower and more useful: developers write an enormous amount of prose, and almost none of it is code.

Commit messages. Pull request descriptions. Code review comments. Slack threads explaining a decision. Documentation. Issue reports. Design notes. Replies to the person who asked why the build is red. That is where dictation pays, and the reason it needs developer-specific features anyway is that this prose is full of symbol names, file paths, and things that must not be autocorrected.

What actually matters, in order

Ranking dictation tools for developers means ranking them on four things most reviews never mention.

Verbatim output where it matters. A terminal is not prose. If your tool capitalizes the first word, converts quotes to smart quotes, or adds a period, the command is broken. This single behavior separates tools that are usable in a developer’s day from tools that are not.
Symbol and file name accuracy. A speech model has never seen your repository. Say “user auth service dot swift” and a general model writes a plausible English approximation. A tool that knows your project writes the file that exists.
Deterministic punctuation and casing. camelCase, snake_case, brackets, pipes, and angle brackets need to come out the same way every time. A model that decides case by context will be right most of the time, which is the worst possible failure rate for something you have to check.
Insertion that survives Electron. VS Code, Cursor, Slack, and Discord are Electron apps and they reject insertion methods that work in native apps. A tool that cannot type into them cannot help with most of your day.

Prices come from each product’s own page, read between July and August 2026. Flit is first because it is the only one that does all four.

The short version

#	Tool	Price	Verbatim terminals	Knows your project	Platforms
1	Flit	$49 once, 2 Macs	Yes, automatic	Indexes it locally	macOS
2	Voibe	$7.50/mo · $149 once	Not stated	Developer Mode for AI editors	Mac, Windows
3	Talon Voice	Free, supporter tiers	Scriptable	Scriptable	macOS and more
4	Superwhisper	Free · $249.99 lifetime	Not stated	No	macOS
5	VoiceInk	$25 to $49 once	Not stated	No	macOS
6	Wispr Flow	Subscription	Not stated	No	Mac, Windows, iOS, Android
7	Whisper, yourself	Free, plus time	You build it	You build it	Anything

1. Flit

Built for this case specifically, which is unusual in a category mostly aimed at general writing.

Verbatim in terminals and editors, automatically. No mode to remember. When the focused app is a terminal or a code editor, the formatting layer stops formatting: your words arrive exactly as spoken, so git rebase --onto main survives instead of becoming “Git rebase. Onto main.”

A local index of your open project. Spoken file and symbol names resolve against what is actually in your repository, so “user auth service” comes out as the file that exists rather than as a phonetic guess. The index is built and read on your machine; nothing about your code is uploaded, which for a lot of employers is the difference between allowed and not.

Deterministic commands. More than 60 spoken punctuation, symbol, and structure commands, resolved by fixed rule rather than model judgment. “Camel case user auth service” is always userAuthService. “Dash dash force” is always --force, because the dash binds rightward on purpose. The complete reference is published, which is something you can only do when the behavior really is fixed.

It types into every app with a cursor including Electron ones, and it runs entirely on your Mac with no account, at $49 once for up to 2 Macs. Limits: macOS 14 or later on Apple silicon, and no file transcription.

Flit for developers →

2. Voibe: Developer Mode, and Windows

The other tool that treats developers as a first-class case, with a Developer Mode aimed at Cursor, VS Code, and Windsurf, and it shipped that before we did. It streams text live on Mac and runs on Windows too, which no fully local Mac tool does.

The costs are an email account, a cloud mode alongside the local one (local on M1 or newer), and $149 for the lifetime tier. If you work across a Mac and a Windows machine, that is the trade worth making.

Flit vs Voibe →

3. Talon Voice: when you want to control, not dictate

A different category, and for some readers the most important tool on this page. Talon replaces the keyboard and mouse with voice, non-speech sounds, and optional eye tracking. It is genuinely capable of driving an editor, navigating code, and writing it, and it is free and local.

The cost is real: scripting is expected, the learning curve is substantial, and it is a commitment rather than an install. If you are dealing with a serious RSI, that investment is usually worth it, and the common setup is both tools: Talon to drive the machine, a dictation app for the prose.

Flit vs Talon Voice →

4. Superwhisper

Local, capable, and the right answer if you also transcribe recordings such as architecture discussions or standups you recorded with consent. Text lands after you stop speaking rather than while you talk, terminal behavior is not publicly stated, and there is no project awareness. $249.99 lifetime, with a free tier and subscriptions.

Flit vs Superwhisper →

5. VoiceInk

Local, no account, from $25, and the source is readable, which is a genuine argument in an environment where you have to justify tools to a security process. No streaming and no project awareness, so expect to fix symbol names by hand.

Flit vs VoiceInk →

6. Wispr Flow

Polished, cross-platform, and cloud. For a developer the cloud question is sharper than for most people: dictating about unreleased work or customer data into a third-party service is exactly the thing your employer’s policy is about. If that is fine where you work and you dictate on several devices, it is the strongest cross-platform option.

Flit vs Wispr Flow →

7. Whisper, yourself

You are the audience most able to build this, and it is a good project: the models are free and excellent. What you are signing up to maintain is the global hotkey, streaming, insertion that survives Electron, formatting, and the fixes when macOS changes. Worth doing once to understand the problem. Worth buying afterwards.

Flit vs rolling your own →

The setup that actually works

Whichever tool you land on, this is the shape most developers converge on after a couple of weeks:

Dictate the prose, type the code. Commit messages, PR descriptions, review comments, docs, and chat by voice. Code by keyboard. This is not a compromise, it is where the speed actually is.
Put the hotkey under a thumb, not a finger you type with.
Add symbol names to your dictionary in week one, as you hit them. Ten real names beat two hundred imagined ones.
Check terminal behavior on day one with a command containing quotes and a double dash. That is the test that fails fastest.
Do not fight it in the editor. If you want voice control of the editor itself, that is Talon, and it is a separate decision.

If you want the practical walkthrough rather than the tool comparison, how to dictate code covers the setup, the spoken casing commands, and the parts that genuinely do not work. For the wider category, see the 15 best dictation apps for Mac.