Developer workflow · 8 min
Voice to text for coding: talk through intent, keep your hands on the hard parts.
Dictation is strongest for prompts, plans, bug reports, comments, and review notes—not for spelling every brace. VoiceToText pastes reviewed speech into the coding tool already under your cursor.
- Cursor & VS Code
- Terminals & chat
- Local transcription
- Review before paste
Use voice for the semantic layer
Speak the outcome, constraints, evidence, and acceptance criteria; type exact symbols and identifiers. That division avoids the most frustrating part of code dictation while making detailed AI-agent prompts, pull-request notes, and debugging narratives much faster to capture.
Start with high-leverage text
The best coding dictation is usually prose that controls code.
Agent and chat prompts
Describe the change, files in scope, constraints, edge cases, and how to verify it. A complete spoken brief is more useful than a terse one-line request.
Bug reproduction
Narrate what you did, what you expected, what actually happened, and the exact environment while the failure is still visible.
Comments and documentation
Explain why a decision exists, summarize a public API, or capture migration guidance, then edit the transcript for identifiers and precision.
Review and handoff notes
Dictate PR feedback, test findings, stand-up notes, and a session handoff without switching away from the diff, terminal, or issue form.
A repeatable pattern
Speak prompts in five passes, then review once.
Begin with the goal: “Add keyboard navigation to the command menu.” Follow with the relevant context: framework, component, current behavior, and files you already inspected. Then name the constraints: preserve public APIs, avoid a new dependency, or keep the feature accessible without JavaScript.
Next, dictate edge cases and acceptance checks. Mention empty states, focus restoration, reduced motion, error handling, and the commands or tests that should pass. End by defining the output you want from the agent—implementation, diagnosis only, or a small plan before edits.
Stop and use the review panel before pasting. Correct paths, function names, issue numbers, and negations. Those few tokens often carry more technical meaning than the rest of the prompt, and a speech model cannot infer a project-specific spelling it has never seen.
Keep it in the active tool
Use the same shortcut in an editor, terminal, browser, or native app.
Place the cursor deliberately
Click the exact chat box, issue field, comment, or document location that should receive the text. VoiceToText returns the transcript to the focused field.
Record in a natural sentence
Press Option+Space by default, or use your custom shortcut. Say complete thoughts and name punctuation only when the literal character matters.
Review technical tokens
Check filenames, package names, flags, commands, URLs, versions, and words such as “not.” Edit them before they can steer an agent or shell in the wrong direction.
Paste, then type the syntax
Press Return to paste. Add code fences, backticks, operators, and exact snippets with the keyboard or let the coding tool generate code from the prose.
Accuracy and safety
Treat a transcript as draft input, especially near a shell.
Do not auto-paste dictated shell commands and immediately run them. A single missing “not,” changed path, or invented flag can turn a harmless request into a destructive operation. Keep review enabled, paste into an editor or prompt box first, and read the final command before execution.
Voice is also a poor way to enter secrets. Never dictate API keys, passwords, recovery codes, or private tokens. Use a password manager or secure input flow that does not expose the secret in a transcript or local history.
For private repositories, choose a local Parakeet or Whisper model so the recording is transcribed on the Mac. Remember that the destination can still be cloud-based: pasting a private prompt into a hosted AI tool sends the text under that tool’s terms, even if speech recognition itself was local.
Choose the right input
Keep typing when token-level precision dominates.
Exact code
Dense syntax, indentation, escaping, generics, regular expressions, and short identifiers are usually faster and safer with a keyboard.
Sensitive values
Credentials and private keys should never enter a dictation transcript, review panel, clipboard, or speech history.
Noisy shared spaces
A keyboard preserves privacy and accuracy when colleagues are talking or when speaking project details aloud would be disruptive.
Small edits
Renaming one symbol or changing a boolean is not a speech task. Reach for voice when the thought is longer than the edit.
Side-by-side
Compare the practical differences.
| Decision point | Dictate | Type |
|---|---|---|
| AI prompts | Goals, context, constraints, examples, and acceptance criteria. | Exact paths, commands, and code samples. |
| Source code | Comments, docstrings, and high-level pseudocode. | Syntax, identifiers, operators, and indentation. |
| Debugging | Reproduction narrative and observations while the bug is visible. | Logs, stack traces, hashes, and precise values. |
| Code review | Reasoning, risks, suggested behavior, and questions. | Inline patches and token-level corrections. |
| Terminal | Explain the task to an agent or draft a command for review. | Inspect and execute the final command yourself. |
Primary sources
Check the claims at the source.
Product behavior changes. These official pages were reviewed on July 27, 2026.
- VoiceToText integration guide ↗
The project’s primary documentation for invoking VoiceToText from other Mac apps with its URL scheme.
- VoiceToText source repository ↗
Public source for the global shortcut, review flow, local engines, and paste behavior described here.
- Apple Voice Control guide ↗
Apple’s primary documentation for a different workflow: navigating the Mac and dictating or editing text with Voice Control commands.
Keep exploring
Related Mac voice-to-text guides.
Try your next coding brief out loud.
Open the prompt box you already use, speak the goal and constraints, check technical tokens, and paste the reviewed transcript.