# How to Dictate in VS Code: Voice Coding & Copilot (2026)

> Dictate in VS Code by voice: use the on-device VS Code Speech extension, or a system-wide tool that types into every app plus resolves your workspace file and folder names. Setup, Copilot voice-prompting, and tips.

- URL: https://www.getvoibe.com/resources/dictate-in-vs-code/
- Author: Ayush
- Published: 2026-06-09 · Updated: 2026-10-12

**TL;DR:** To dictate in [VS Code](https://code.visualstudio.com), you have two good options. Microsoft's free **VS Code Speech** extension adds on-device dictation to the editor and GitHub Copilot Chat (including "Hey Code" activation). Or run a **system-wide** Mac dictation tool like [Voibe](https://www.getvoibe.com), which types into every VS Code surface _and_ every other app, and resolves your workspace's file and folder names as you speak. Pick the extension if you live entirely in VS Code; pick a system-wide tool if you want one hotkey everywhere plus workspace-aware accuracy.

If you also use Cursor, the same system-wide setup carries over — see our companion guide on [how to dictate in Cursor](https://www.getvoibe.com/resources/dictate-in-cursor/). This guide covers the VS Code Speech extension honestly, then the system-wide setup, Developer Mode file resolution, and real voice-prompt examples for Copilot.

> **Key takeaway:** Dictate in VS Code with Microsoft's on-device VS Code Speech extension (editor + Copilot Chat + 'Hey Code'), or a system-wide tool that works in every app and resolves your workspace file and folder names via Developer Mode.

> **Tip:** Quick test of whether a system-wide tool is worth it: count how many apps outside VS Code you'd want to dictate into today — the browser, Slack, email, your terminal, Cursor. VS Code Speech covers none of those; a system-wide tool covers all of them with the same hotkey.

## Where You Can Dictate in VS Code

VS Code has several inputs, and which ones accept voice depends on your tool. A system-wide dictation tool works in all of them because it inserts text wherever the cursor is; the VS Code Speech extension covers the editor and Copilot Chat:

| VS Code surface | What you dictate | VS Code Speech | System-wide tool |
| --- | --- | --- | --- |
| **Copilot Chat** | Codebase questions, change requests, debugging | Yes (mic + "Hey Code") | Yes |
| **Copilot inline / Edits (Cmd+I)** | Targeted edits, multi-file changes | Partial | Yes |
| **The code editor** | Comments, docstrings, Markdown, strings | Yes (Ctrl+Alt+V) | Yes |
| **Integrated terminal** | Commands, branch names | No | Yes |
| **Source Control commit box** | Commit messages | No | Yes |

VS Code's AI lives in **GitHub Copilot** — Copilot Chat, inline chat (Cmd+I), and Copilot's Edits and Agent modes for multi-file work. All of them are driven by prose, which is what dictation speeds up. The VS Code Speech extension hooks voice into Copilot Chat and editor dictation; a system-wide tool extends it to the terminal, the commit box, and every app outside VS Code.

## VS Code Speech Extension vs a System-Wide Dictation Tool

Unlike Cursor's native voice mode, VS Code's official voice option is genuinely strong, so this is a fair comparison rather than a one-sided one. Microsoft's [VS Code Speech](https://code.visualstudio.com/docs/configure/accessibility/voice) extension processes audio locally (no internet required), dictates into the editor (Voice: Start Dictation in Editor, Ctrl+Alt+V), powers Copilot Chat voice, and supports "Hey Code" keyword activation. If you spend your whole day inside VS Code, it is a legitimate, private, free choice.

The case for a system-wide on-device tool is not about privacy here — both run locally — it is about scope and accuracy:

| Dimension | VS Code Speech extension | System-wide on-device (Voibe) |
| --- | --- | --- |
| Works in the editor + Copilot Chat | Yes | Yes |
| Works in the terminal + commit box | No | Yes |
| Works in every other app (browser, Slack, email, Cursor) | No | Yes |
| Processing location | On-device | On-device |
| Resolves your workspace's file names | No | Yes (Developer Mode) |
| Custom vocabulary for libraries / APIs | No | Yes |
| Activation | "Hey Code" / mic button | Hold-to-talk hotkey |

The honest verdict: if VS Code is the only place you dictate, the extension is hard to beat for free. The moment you want to dictate in your browser, your chat apps, your terminal, or a second editor — and to have spoken file names land as real identifiers — a single system-wide tool replaces a per-app patchwork. The two even coexist: some developers keep VS Code Speech for "Hey Code" and use a system-wide tool everywhere else.

## Step 1: Install a System-Wide Dictation Tool

The setup mirrors any Mac dictation tool; this guide uses [Voibe](https://www.getvoibe.com) for its on-device processing and the Developer Mode workspace resolution that plain dictation lacks.

1. Download Voibe from [getvoibe.com](https://www.getvoibe.com) (or the [direct .dmg](https://voibe.s3.us-east-1.amazonaws.com/releases/current/voibe.dmg)) and drag it to Applications.
2. Launch it. On Apple Silicon (M1–M4, macOS 13+) it downloads a local Whisper model (~2 GB) on first run.
3. No account, and no internet needed after the model downloads.

For the full install walkthrough, see our [Voibe setup guide](https://www.getvoibe.com/resources/getting-started-with-voibe/).

> **Info:** Requirements: a Mac with Apple Silicon (M1, M2, M3, or M4) running macOS 13 Ventura or later, and about 2 GB of free disk space. The VS Code Speech extension, by contrast, runs on any platform VS Code supports — so on Windows or Linux it remains a strong in-editor option.

## Step 2: Grant Permissions and Set a Hold-to-Talk Hotkey

A system-wide tool needs two macOS permissions to type into VS Code:

1. **Accessibility** — to insert text (System Settings > Privacy & Security > Accessibility, then enable the app).
2. **Microphone** — to capture speech (granted on first use, or under System Settings > Privacy & Security > Microphone).

Pick a hotkey you can hold while your hands rest on the keyboard. Voibe defaults to holding **Fn**: press and hold, speak, release, and the text appears at the cursor. Reassign it in settings if Fn clashes with your layout — see our [Mac dictation keyboard shortcuts guide](https://www.getvoibe.com/resources/mac-dictation-keyboard-shortcuts-guide/) for options and conflicts. Hold-to-talk suits coding because your hands return to the keys the instant you release.

## Step 3: Enable Developer Mode for File and Folder Resolution

This is the capability the VS Code Speech extension does not have, and the reason a system-wide tool can be more accurate inside VS Code, not just broader. Open Voibe's settings and toggle **Developer Mode** on. It detects your open VS Code (or Cursor) window and resolves file names, folder names, and project-specific terms from your workspace as you dictate.

Plain dictation transcribes identifiers literally: say "auth middleware dot t s" and you get those words. Developer Mode matches them against your open workspace and inserts `authMiddleware.ts`. The same applies to folders, components, and any term in your project tree — so a dictated comment, commit message, or Copilot prompt references the real file without manual fixing.

## Real Voice Examples for Copilot, the Editor, and Commits

Here is what dictating into each VS Code surface looks like with a system-wide tool. Hold your hotkey, speak, release.

### Copilot Chat — Codebase Questions and Changes

Click into the Copilot Chat box and dictate:

- _"Why does the checkout request fail when the cart is empty? Look at the cart store and the checkout page."_
- _"Add a loading state to the Pay button and disable it while the request is in flight."_

### Copilot Inline (Cmd+I) — Targeted Edits

Select a block, press Cmd+I, and dictate the change:

- _"Convert this to use async/await and add a try-catch around the fetch."_

### The Editor — Comments, Docstrings, Markdown

Place your cursor in the file and dictate prose directly: a docstring above a function, a section in your README, or a TODO note. With Developer Mode on, referencing other files by name stays accurate.

### The Terminal — Commit Messages

In the integrated terminal or the Source Control box, dictate a commit message: _"fix: prevent duplicate submissions on the checkout button."_

Keep prompts short and structured — voice handles a focused two-sentence instruction far better than a long run-on. For a repeatable structure, use the **Five-Part Voice Prompt** framework (Goal, Inputs, Constraints, Example, Output) in our [voice-prompt AI guide](https://www.getvoibe.com/resources/voice-prompt-ai/), and the Talk-Draft-Polish loop in our [voice input workflow guide](https://www.getvoibe.com/resources/voice-input-workflow/).

## Tips for Dictating in VS Code More Accurately

- **Add a custom vocabulary for your stack.** Library, framework, and API names (e.g. "Vitest", "Prisma", "useQuery") are what dictation gets wrong. Add them once.
- **Let Developer Mode handle file names.** Say the file name naturally rather than spelling the path; workspace resolution maps it to the real identifier.
- **Decide your division of labor.** If you like "Hey Code," keep the VS Code Speech extension for chat activation and use a system-wide tool for the editor, terminal, and other apps.
- **Dictate in short bursts.** Ten-to-thirty-word phrases are most accurate; pause between thoughts.
- **Speak the goal, then constraints.** "Paginate the users table, twenty per page, server-side" beats narrating implementation steps.
- **Use a decent microphone.** A basic USB mic noticeably reduces errors on technical terms.
- **Edit with the keyboard.** Voice is fastest for the first draft of a prompt or comment; fix the last few words by hand.

## Troubleshooting: When Dictation Isn't Working in VS Code

### A system-wide tool isn't typing into VS Code

Check Accessibility permission first: System Settings > Privacy & Security > Accessibility, and confirm the app is enabled. If it is on but still not typing, remove and re-add it to reset the permission — this resolves most cases after an update.

### The VS Code Speech extension isn't transcribing

Confirm the extension is installed and that you have downloaded a speech model when prompted. "Hey Code" requires the keyword-activation setting (accessibility.voice.keywordActivation) to be enabled. Editor dictation is triggered with Voice: Start Dictation in Editor (Ctrl+Alt+V).

### File names aren't resolving

Confirm Developer Mode is on and VS Code is the frontmost window with the workspace open. Resolution matches files in the open project; add the term to your custom vocabulary as a fallback.

### Technical terms are mis-transcribed

Add the library, framework, or API names to your custom vocabulary. General speech models don't know "Zod" or "Drizzle" until told.

### Dictation feels slow

On-device transcription shares the Neural Engine with other apps. Close memory-heavy apps or pick a smaller local model on an 8 GB Mac.

## Tools That Make Dictating in VS Code Easier

- **[VS Code Speech](https://code.visualstudio.com/docs/configure/accessibility/voice)** (Microsoft) — free, on-device, covers the editor and Copilot Chat with "Hey Code." The best free option if you work only in VS Code; no workspace file resolution or custom vocabulary, and VS Code-only.
- **[Voibe](https://www.getvoibe.com)** — system-wide and on-device, with Developer Mode workspace resolution and custom vocabulary. Works in VS Code and every other app. $199 lifetime or $9.90/month, a free plan with limited words, and a 7-day full trial. See our [best dictation software for developers](https://www.getvoibe.com/resources/best-dictation-software-for-developers/) guide.
- **[Apple Dictation](https://www.getvoibe.com/resources/apple-dictation-review/)** — free, system-wide baseline, but with a session timeout and no custom vocabulary or workspace awareness.
- **[Wispr Flow](https://www.getvoibe.com/resources/wispr-flow-review/)** — polished cloud dictation with AI formatting; cross-platform but cloud-based, so weigh that for proprietary code. $144/year.
- **[Superwhisper](https://www.getvoibe.com/resources/superwhisper-review/)** — on-device Whisper modes plus optional cloud LLM cleanup; $249.99 lifetime, no dedicated IDE file resolution.

Using the AI editor Cursor instead of VS Code? See our companion [how to dictate in Cursor](https://www.getvoibe.com/resources/dictate-in-cursor/) guide. For the architecture comparison, see [cloud vs local dictation](https://www.getvoibe.com/resources/cloud-vs-local-dictation/) and [offline dictation privacy on Mac](https://www.getvoibe.com/resources/offline-dictation-privacy-mac/).

Dictation is one layer of an agent workflow rather than the whole of it. For how it fits with Claude Code, browser verification, and automated code review, see our [five-tool agentic engineering stack](https://www.getvoibe.com/resources/best-agentic-engineering-tools/).

## Frequently Asked Questions About Dictating in VS Code

### Basics

**Can you dictate in VS Code?**
Yes — with Microsoft's on-device VS Code Speech extension (editor + Copilot Chat + "Hey Code"), or with any system-wide Mac dictation tool that types into every VS Code surface and every other app.

**Does VS Code have built-in voice dictation?**
Not in core, but the official VS Code Speech extension adds it: on-device speech-to-text for the editor and Copilot Chat, with keyword activation. It works only inside VS Code.

### Setup

**Is the VS Code Speech extension private?**
Yes. It processes audio locally and never sends recordings to an online service, so it works offline — a safe choice for proprietary code. A system-wide on-device tool offers the same privacy plus broader coverage.

**What is Developer Mode?**
A Voibe setting that resolves spoken file names, folder names, and project terms from your open VS Code workspace to their exact spelling — turning "auth middleware" into authMiddleware.ts automatically.

### Workflow

**How do I dictate into Copilot Chat?**
With VS Code Speech, use the mic button or "Hey Code." With a system-wide tool, click the chat box, hold your hotkey, and speak — the same gesture works in inline chat, the editor, and the terminal.

**Should I use the extension or a system-wide tool?**
Use the extension if VS Code is the only place you dictate. Use a system-wide tool if you also dictate in the browser, Slack, email, the terminal, or Cursor, and want workspace file-name resolution.

## Start Dictating in VS Code

VS Code dictation comes down to scope. Microsoft's VS Code Speech extension is a genuinely good, on-device, free option — if VS Code is the only place you talk to your computer. A system-wide on-device tool wins the moment you want one hotkey across every app and spoken file names that resolve to real identifiers in your workspace.

[Voibe](https://www.getvoibe.com) is the on-device option built for that: [download it free](https://voibe.s3.us-east-1.amazonaws.com/releases/current/voibe.dmg) (Voibe Free plus a 7-day full trial), enable Developer Mode, and dictate your next Copilot prompt — and your next Slack message and commit — with the same hotkey.

**Keep going:**

- [How to dictate in Cursor](https://www.getvoibe.com/resources/dictate-in-cursor/) — the AI-editor companion to this guide
- [How to dictate in Linear & Jira](https://www.getvoibe.com/resources/dictate-in-linear-jira/) — voice ticket-writing
- [How to dictate in Slack](https://www.getvoibe.com/resources/dictate-in-slack/) — faster messages and replies
- [How to voice-prompt ChatGPT, Claude, and Cursor](https://www.getvoibe.com/resources/voice-prompt-ai/) — the Five-Part Voice Prompt framework
- [The voice input workflow](https://www.getvoibe.com/resources/voice-input-workflow/) — the Talk-Draft-Polish loop
- [Best dictation software for developers](https://www.getvoibe.com/resources/best-dictation-software-for-developers/) — the full buyer's view
- [Getting started with Voibe](https://www.getvoibe.com/resources/getting-started-with-voibe/) — complete setup guide
- [How to dictate in Microsoft Word](https://www.getvoibe.com/resources/dictate-in-microsoft-word/) — the Dictate button, and the paths that work without it

> **Tip:** If you already use VS Code Speech and like it, you don't have to switch — add a system-wide tool for everything outside VS Code and let Developer Mode handle file names. The two work together.

## Frequently asked questions

### Can you dictate in VS Code?

Yes, two ways. Microsoft's free VS Code Speech extension adds on-device dictation to the editor (Voice: Start Dictation in Editor, Ctrl+Alt+V) and to GitHub Copilot Chat, including 'Hey Code' hands-free activation. Separately, any system-wide Mac dictation tool — like Voibe, Apple Dictation, or Wispr Flow — types into every VS Code surface plus every other app you use. The system-wide route means one tool and one hotkey everywhere, not a dictation feature that only works inside VS Code.

### Does VS Code have built-in voice dictation?

Not in the core editor, but Microsoft publishes the official VS Code Speech extension that adds it. The extension does speech-to-text for Copilot Chat and editor dictation, processes audio locally on your machine with no internet required, and supports 'Hey Code' keyword activation to start a voice chat. It is a solid option if you work entirely inside VS Code. Its limits are that it only works in VS Code, does not resolve your workspace's file names, and has no custom vocabulary.

### Is the VS Code Speech extension on-device?

Yes. Per Microsoft's documentation, VS Code Speech computes voice locally on your machine and recordings are never sent to an online service, so it works offline. That makes it a privacy-safe choice for proprietary code. The trade-off versus a system-wide on-device tool like Voibe is scope: VS Code Speech only works inside VS Code, whereas a system-wide tool also dictates in your browser, Slack, email, terminal, and other editors, and adds workspace file-name resolution.

### What is Voibe Developer Mode and why does it help in VS Code?

Developer Mode is a Voibe setting that detects your open VS Code or Cursor window and resolves spoken file names, folder names, and project terms to their exact spelling from your workspace. Plain dictation — including the VS Code Speech extension — writes the literal words, so 'auth middleware dot ts' stays as text; Developer Mode inserts authMiddleware.ts. This removes the most common cleanup step when dictating code comments, commit messages, or Copilot prompts that reference real files.

### How do I dictate into GitHub Copilot Chat in VS Code?

With the VS Code Speech extension, click the microphone in the Copilot Chat box or say 'Hey Code' to start a voice prompt. With a system-wide tool, click into the Copilot Chat input, hold your dictation hotkey, speak the prompt, and release. The system-wide approach lets you dictate the same way into Copilot inline chat (Cmd+I), Copilot Edits, the editor, and the terminal — anywhere you'd type — rather than only the chat box.

### Which dictation tool is best for VS Code on Mac?

If you only ever work in VS Code and want a free built-in option, the VS Code Speech extension is on-device and capable. If you want one tool for every app plus workspace-aware accuracy, Voibe runs Whisper locally on Apple Silicon ($199 lifetime or $9.90/month), types into VS Code and every other app, and its Developer Mode resolves your project's file and folder names. Apple Dictation is the free system-wide baseline but has a session timeout and no custom vocabulary; Wispr Flow is a cloud alternative.