Skip to main content

How-to

Dictation in Cursor on a Mac

Cursor looks like VS Code and takes VS Code extensions, with one category of exception that happens to include the dictation one.

Last updated: 2026-08-29

The prompt box is where Cursor absorbs the most typing. Long requirements, edge cases, and the explanation of what the model got wrong last time are all prose, and prose is what dictation is for.

The Cursor-specific trap: the speech extension will not install

Search the Extensions view in Cursor for VS Code Speech and you will not find Microsoft's version of it. Cursor installs extensions from the Open VSX registry rather than the Microsoft Marketplace, and Microsoft's own extensions are not published there. Cursor's documentation covers this and points at first-party replacements for the ones it can ship itself. Dictation is not one of the replacements, so on Cursor you use a system-level tool, not an extension.

If a search result offers a lookalike "speech" extension in Cursor, check the publisher before installing. It is not Microsoft's, and it does not carry Microsoft's shortcut or behaviour.

Dictate a prompt in Cursor

  1. Turn Dictation on once: System Settings → Keyboard → Dictation. Full steps in enable dictation on macOS.
  2. Open the chat panel and click into the prompt box so the cursor is blinking there.
  3. Start Dictation and speak the request in full: the goal, the constraint, and what you already tried.
  4. Stop Dictation. Read the transcript before submitting, because a mis-transcribed file name sends the model to the wrong file.

The second trap: the send keys are not VS Code's

Cursor's own keyboard reference does not use the plain chat-app model where Return sends and Shift+Return makes a newline. Return and Command+Return are bound to different submit behaviours in the chat panel. Before you dictate a long multi-paragraph prompt, open Cursor's keyboard shortcuts reference and confirm what your version does with Return, or dictate into a scratch file and paste. Losing a two-minute spoken prompt to an accidental submit happens once and teaches the lesson permanently.

What to dictate, and what to keep on the keyboard

  • Dictate: requirements, edge cases, the reproduction, and the reason the last attempt was wrong. This is the bulk of a good prompt and it is entirely prose.
  • Type: file paths, symbol names, and anything inside backticks. Speech gets casing and separators wrong, and a wrong path is worse than no path because the model will act on it.
  • Dictate: the acceptance criteria list. Then edit the formatting.

If nothing types at all

  • Cursor is a separate application from Visual Studio Code as far as macOS permissions are concerned. Granting Code microphone or accessibility access does nothing for Cursor. Check System Settings → Privacy & Security for Cursor by name.
  • Dictation dead everywhere, not just Cursor: dictation not working on Mac.

One hotkey that survives the editor switch

An editor-specific extension stops working the day you change editors, and editors are changing often right now. A system-level hold-to-dictate hotkey works in Cursor, in the editor you move to next, and in the browser tab where the ticket lives. Voice Type runs the model on your Mac: voice typing for Mac.

Keep going

Sources

Try Voice Type (7-day free trial)

Try it on your own work

Voice Type is on-device dictation for macOS. Hold a hotkey, speak, and release to insert text in any app. Your audio never leaves your Mac. Free for 7 days, then $19.99 once on the Mac App Store. No subscription and no account.

Start the free trial