How to dictate code with your voice
Dictating literal code, brackets, camelCase, operators, and indentation, is slower and more error-prone than typing it, and no dictation app fully solves that. What does work is dictating the natural-language parts of coding: AI prompts, comments, docstrings, commit messages, and issues. The realistic workflow is hybrid: talk for prose, type for syntax, and let an AI assistant turn your spoken intent into code.
What voice is good for in coding
- Prompts to AI assistants in Cursor, Claude, or ChatGPT. This is the biggest win: describe the change out loud in detail.
- Comments and docstrings. Explaining intent is faster spoken.
- Commit messages and PR descriptions. Pure prose.
- Issues, tickets, and Slack. Everyday developer writing.
What voice is bad for
- Exact syntax. Dictating
for (let i = 0; i < n; i++)is painful. - Precise names. Function and variable names get mangled unless you add them to a dictionary.
- Refactors that need cursor precision. The keyboard wins.
The hybrid workflow
- Put your cursor in the AI chat pane (for example in Cursor or VS Code).
- Dictate a full, contextual prompt describing what you want.
- Let the assistant generate the code; you type the small precise edits.
- Dictate the commit message and PR description.
Add your stack's terms (library names, APIs, product names) to a custom dictionary so they stop getting mistranscribed.
Try the hybrid workflow
Dictate your prompts and prose, type your syntax. Start on the free plan, no credit card.
Free plan, no credit card required.
Frequently asked questions
It can dictate natural language accurately, but exact code syntax is still faster typed. Pair dictation with an AI coding assistant: speak the intent, let the AI write the code.
Add them to your custom dictionary so Wispr Flow spells them the way your codebase does.
For prompts, comments, and docs, yes. For typing precise syntax, no. Use it where it wins.
Related: in Cursor and VS Code · for developers · custom dictionary