Dictation for VS Code on Mac: AI Prompts, Issues, and Dev Notes

Short answer

Dictation in VS Code is best for the writing around code: Copilot Chat prompts, bug reports, repro steps, PR notes, review comments, issue drafts, and short planning notes. Use the keyboard for exact code, shell commands, paths, secrets, migrations, and anything that can change files or production state. VS Code has its own Microsoft Speech extension for local voice input, while broader Mac dictation tools can help when you want the same voice workflow across VS Code, Cursor, terminals, email, and docs.

The search for dictation for VS Code on Mac usually starts with a narrow hope: can I talk to the editor instead of typing everything? The useful answer is yes, but only if you separate intent from execution.

Voice is good at explaining what you want. It is good at giving Copilot context, describing a bug, writing a PR summary, and capturing the thing you just learned while debugging. It is bad at being trusted blindly for punctuation-heavy code, flags, quoted strings, file paths, API keys, destructive commands, and exact syntax.

This page was checked against current public pages on June 12, 2026, including the VS Code Speech extension, VS Code Copilot Chat documentation, the GitHub Copilot Chat cheat sheet, Wispr Flow's vibe coding page, Superwhisper's Mac voice-to-text page, Apple's Mac Dictation guide, and Aqua Voice's FAQ.

Where voice fits in VS Code

Think of voice as the planning layer. It should make the high-context parts easier without removing the review step that keeps coding safe.

Developer task	Good to dictate	Type or review carefully
Copilot Chat prompt	Goal, constraints, current behavior, expected behavior, relevant files, and what not to change.	File names, function names, flags, data shape, and any instruction that could trigger broad edits.
Bug reproduction	Steps, environment, observed result, expected result, logs to inspect, and what you already tried.	Error codes, package versions, branch names, stack traces, and command output.
PR summary	Why the change exists, the main files touched, risk areas, and how you tested it.	Exact issue IDs, migration notes, API behavior, and security-sensitive details.
Code comment draft	The reason a block exists, a caveat, or a short warning for the next maintainer.	Comments that claim guarantees the code does not actually enforce.
Issue or ticket note	Problem, scope, owner, acceptance criteria, and follow-up questions.	Customer names, credentials, private URLs, internal incidents, and legal or security claims.
Terminal or task prompt	The intent around the command and the review checklist before running it.	The command itself, destructive flags, paths, secrets, deploy steps, and rollback commands.

If a sentence can safely be wrong for a few seconds while you edit it, voice is a good candidate. If a sentence can run, delete, deploy, expose, or bill, keep the final action deliberate.

VS Code voice options on Mac

There are two categories to compare: voice built into the VS Code workflow, and system-wide Mac dictation that happens to work inside VS Code.

Option	Best fit	Check first
VS Code Speech	Developers who want Microsoft speech-to-text inside VS Code chat and editor fields. The marketplace page says the extension adds speech-to-text and text-to-speech, needs no internet connection, processes voice audio locally, shows a microphone icon in Copilot Chat interfaces, and supports editor dictation.	Language support, VS Code setup, keybindings such as Cmd+I for chat and Cmd+Alt+V for editor dictation, and whether it covers non-VS Code apps.
Apple Dictation	A free baseline for short low-risk text in fields where macOS dictation behaves well.	Apple says users can check whether general text Dictation is processed on device and not sent to Siri servers, but the destination and setting matter.
Superwhisper	Power users who want Mac-wide voice-to-text, offline paths on Apple Silicon, custom behavior, and text at the cursor across apps including VS Code and Xcode.	Whether the configuration helps your daily coding flow or adds setup work.
Amical	Mac users comparing open-source AI dictation, model choices, app modes, and a free local plus paid cloud pricing model. Its pricing page lists unlimited local dictation on the free plan and paid cloud plans separately.	Apple Silicon/macOS requirements, optional cloud cleanup settings, and how Power Modes behave in coding apps.
Wispr Flow	Developers who want polished voice prompts across IDEs, terminals, and devices as part of a broader hosted voice platform.	Wispr's privacy page says transcription always happens in the cloud, so check Privacy Mode and account controls before sensitive prompts.
Aqua Voice	Hosted technical dictation for prompts, code-adjacent writing, product names, and fast system-wide text insertion.	Aqua's FAQ says it is cloud-based, needs a connection, and processes audio in the cloud.
Unspoken	Mac developers who want local-first capture for rough prompts, dev notes, issue drafts, and PR summaries before pasting or editing in VS Code.	Best as a private first-draft step. Keep exact code and commands under manual review.

A safe developer dictation workflow

Open the right targetStart in Copilot Chat, an issue draft, a Markdown note, a PR description, or a scratch file. Avoid dictating into a terminal prompt by default.
Say the job type firstStart with "Copilot prompt," "bug repro," "PR summary," or "review note" so the draft has a shape.
Speak context, not commandsDescribe the goal, constraints, relevant files, and known failures. Do not rely on voice for the exact command or migration step.
Mark dangerous parts out loudSay "check path," "verify flag," "do not run yet," "fake secret," or "review before applying" where the note needs a deliberate pause.
Use Copilot context deliberatelyGitHub's Copilot Chat cheat sheet lists slash commands and variables such as @workspace for project context. Add context intentionally instead of dumping a vague paragraph.
Edit before actionNames, paths, commands, tests, package versions, error messages, and security details deserve keyboard review before they become code or instructions.

The goal is not hands-free coding. The goal is faster thinking-to-text while the risky parts still get normal developer scrutiny.

Prompt and note templates that work well by voice

Copilot Chat prompt

Use this when you need help without losing control: "Goal, current behavior, expected behavior, relevant files, constraints, tests to preserve, and what not to change." After dictating, add exact file names and symbols by hand.

Bug reproduction

Use this after a failed run: "Environment, branch, steps, observed result, expected result, latest error, what I already tried, next thing to inspect." Paste exact logs only after reviewing them for secrets.

PR summary

Use this before opening a pull request: "Why this change exists, main approach, files touched, user-visible behavior, tests run, risks, and follow-up work." Then check issue IDs, test names, and migration notes manually.

Review comment

Use this when the idea is clear but the wording is slow: "Concern, why it matters, suggested change, and whether it is blocking." Edit the tone before posting.

Scratchpad for agentic coding

Use this before asking an agent to edit: "Objective, files in scope, files out of scope, constraints, acceptance checks, and stop conditions." The stop conditions are important. Voice makes it easy to ask for too much.

Privacy and review checks before real work

Developer dictation often contains more sensitive material than a normal email. You may say internal URLs, customer names, stack traces, feature plans, incident details, credentials by accident, or a half-formed security theory that should not leave your machine.

Does the tool process audio locally, in the cloud, or through a mixed path?
Does cleanup or app context send transcript text, clipboard content, or window content to a provider?
Does your company allow code, customer data, logs, or incident notes in that tool?
Can you use fake paths, fake secrets, and sanitized logs for the first test?
Can you explain what happens before the text enters Copilot Chat, an issue tracker, a terminal, or a PR?

Unspoken fits when the first draft should stay close to the Mac: a rough prompt, an issue note, a PR summary, or a scratchpad paragraph you will edit before sharing. Choose VS Code Speech when you want local voice input inside VS Code itself. Choose hosted tools when cross-device polish, team workflows, or technical dictation quality matter more than keeping the first capture step local.

FAQ

Can I dictate directly in VS Code on Mac?

Yes. Microsoft's VS Code Speech extension adds speech-to-text to VS Code, including chat and editor dictation. Its marketplace page says voice audio is processed locally and no internet connection is required.

Should developers dictate code?

Usually no. Dictate the context around code: prompts, repro steps, PR notes, comments, and review drafts. Type or carefully review exact syntax, commands, file paths, secrets, and migrations.

What is the best dictation tool for Copilot prompts?

Start with VS Code Speech if you mainly work inside VS Code. Test a Mac-wide tool such as Unspoken, Superwhisper, Amical, Aqua, or Wispr Flow when you want the same voice workflow across VS Code and other apps.

Is cloud dictation safe for coding notes?

It depends on the work and policy. Hosted tools can be useful, but code prompts may include customer data, logs, internal URLs, or secrets. Use sanitized tests first and check processing, retention, and admin controls.

Where does Unspoken fit?

Unspoken fits Mac developers who want local-first rough capture for prompts, issues, PR summaries, and dev notes before editing the final text in VS Code or another tool.

Speak the first draft into your Mac apps

Unspoken is for Mac users who want to capture rough notes, replies, prompts, and longer drafts locally, then edit normally.

Download Unspoken for Mac