How to Dictate in Cursor: Voice-Prompt the AI Editor (2026)

TL;DR: To dictate in Cursor, run a system-wide Mac dictation tool, put your cursor in any Cursor input — the Agent or Composer prompt, a Cmd+K inline edit, the chat panel, or the code editor itself — hold your dictation hotkey, and speak. Cursor 2.0 added a built-in voice mode, but it drops text only into the Agent prompt; a system-wide on-device tool like Voibe types into every surface, keeps your code on your machine, and resolves your project's file and folder names as you speak. This guide covers the full setup, Developer Mode file resolution, real voice-prompt examples for Cmd+K / Composer / Agent, and how the system-wide approach compares to Cursor's native voice.

This is the killer use case for voice on a Mac: dictation is faster than typing for prose, and AI prompts are prose. Speaking a multi-file Composer instruction is far quicker than typing it — once your tool can spell your file names correctly.

Cursor is an AI-first code editor (a fork of VS Code) with several places you type — and therefore several places you can dictate. A system-wide dictation tool works in all of them because it inserts text wherever your cursor is, exactly like a keystroke:

Cursor's Cmd+K turns a selection into a diff from a natural-language instruction, Composer (Composer 2 shipped in 2026) makes coordinated edits across multiple files, and Agent can read the codebase, run shell commands, and iterate until a task is done. All three are driven by prose you write — which is exactly what dictation accelerates. The catch is that Cursor's built-in voice mode only fills the Agent prompt, so to dictate into Cmd+K, the chat, or the editor itself you need a system-wide tool.

Cursor 2.0 introduced a native voice mode: you hold to speak, release to transcribe, and the text drops into the Agent input. It is genuinely useful for firing off a quick agent prompt without typing. But it is scoped narrowly, and two limitations matter for serious coding-by-voice.

It only targets the Agent prompt. Cursor's voice mode does not type into Cmd+K, the chat panel, the editor, or the terminal, and users on the Cursor community forum report it does not support @-file mentions, model selection, or mode switching by voice. It is prompt dictation, not editor control.

Its processing location is undocumented. Cursor has not published whether its voice transcription runs on-device or streams audio to a server. For a tool you point at a proprietary codebase, that matters: your spoken prompts routinely contain file names, function names, and architecture details. A cloud transcription step sends all of that off your machine.

A system-wide on-device tool addresses both. It types into every surface (and every other app on your Mac), and it runs the speech model locally so audio never leaves the device. Here is the honest comparison:

The pragmatic answer: use Cursor's native voice for throwaway agent prompts if you like it, and a system-wide on-device tool as your primary driver for everything else. The rest of this guide sets up the system-wide path.

Any system-wide Mac dictation tool will type into Cursor. This guide uses Voibe because it runs on-device and has the workspace-aware Developer Mode that makes voice-prompting Cursor reliable; the same steps apply in spirit to alternatives covered at the end.

1. Download Voibe from getvoibe.com (or the direct .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. There is no account to create and no internet needed after the model downloads.

For the full install walkthrough including the first-launch security prompt, see our Voibe setup guide.

A system-wide tool needs two macOS permissions to work inside Cursor:

1. Accessibility — lets the tool insert text into Cursor (System Settings > Privacy & Security > Accessibility, then enable the app).
2. Microphone — lets it capture your speech (granted on first use, or System Settings > Privacy & Security > Microphone).

Then pick a hotkey you can comfortably hold while your hands rest on the keyboard. Voibe defaults to holding the Fn key: press and hold, speak, release, and the text appears at your cursor. If Fn conflicts with your keyboard layout, set a different key in settings — a held right-Command or a custom combination works well. For a deeper look at hotkey options and conflicts, see our Mac dictation keyboard shortcuts guide.

Hold-to-talk is the right pattern for coding: you keep one hand on the hotkey, dictate a prompt or comment, release, and your hands are already back on the keyboard to edit.

This is the step that makes voice-prompting Cursor actually work, and it is the feature no native editor voice mode offers. Open Voibe's settings and toggle Developer Mode on. Once enabled, Voibe detects your open Cursor (or VS Code) window and resolves file names, folder names, and project-specific terms from your workspace as you dictate.

The problem it solves: spoken identifiers don't transcribe cleanly. Say "update user service dot t s" and a normal dictation tool writes exactly that. Developer Mode matches the words against your actual workspace and inserts userService.ts. The same applies to folders, components, and any term that appears in your project tree.

Why it matters for Cursor specifically: the single biggest friction in voice-prompting an AI editor is getting it to reference the right files. A prompt like "refactor the auth handler in userService and update its test" only works if "userService" lands as the real filename. Developer Mode turns that from a manual cleanup step into something automatic.

Here is what dictating into each Cursor surface looks like in practice. Hold your hotkey, speak the instruction, release, and (where relevant) submit.

Cmd+K — Targeted Inline Edit

Select a block of code, press Cmd+K, then dictate the change:

• "Refactor this function to use async/await instead of callbacks, and add error handling with a try-catch block."
• "Extract these three validation checks into a helper called validateInput and call it here."

Composer — Coordinated Multi-File Change

Open Composer and dictate a change that spans files. This is where voice wins most, because multi-file instructions are long to type:

• "In the checkout flow, add a loading state to the Pay button and disable it while the request is in flight. Update the button component and the checkout page that uses it."

Agent — Delegated Task

Dictate a task and let the agent plan and execute:

• "Add a rate limiter to the public API routes, write tests for it, and run them."

The Editor and Terminal

Outside the AI surfaces, dictate directly: a docstring above a function, a Markdown section in your README, or a commit message in the terminal ("fix: prevent duplicate submissions on the checkout button").

Keep prompts to short, structured chunks — voice transcription handles a focused two-sentence instruction far better than a 60-word run-on. For a repeatable structure to dictate by, use the Five-Part Voice Prompt framework (Goal, Inputs, Constraints, Example, Output) from our voice-prompt AI guide, and pair it with the Talk-Draft-Polish loop in our voice input workflow guide.

• Add a custom vocabulary for your stack. Library names, API endpoints, and product terms (e.g. "Tanstack", "Supabase", "useMutation") are the words dictation gets wrong. Add them once so they transcribe correctly every time.
• Let Developer Mode handle file names. Don't spell out paths — say the file name naturally and let workspace resolution map it to the real identifier.
• Speak the goal, then the constraints. "Add pagination to the users table — twenty per page, server-side" lands better than narrating implementation detail.
• Dictate in short bursts. Ten-to-thirty-word phrases transcribe most accurately. Pause between thoughts rather than chaining clauses.
• Use a decent microphone. Even a basic USB mic cuts errors on technical terms versus the built-in mic in a noisy room.
• Edit with your hands. Voice is fastest for the first draft of a prompt or comment; fix the last 5% by keyboard. The hold-to-talk hotkey keeps your hands in position.
• Keep proprietary code on-device. If your codebase is confidential, use an on-device tool so spoken file and function names are never transmitted.

Text isn't appearing in Cursor

This is almost always a missing Accessibility permission. Open System Settings > Privacy & Security > Accessibility and confirm your dictation app is enabled. If it is enabled but still not typing, remove it from the list and re-add it to reset the permission — this fixes most cases after an app update.

File names aren't resolving

Confirm Developer Mode is toggled on and that Cursor is the frontmost window with the workspace open. Resolution works against the files in your open project; a file that isn't part of the workspace won't be matched. Adding the term to your custom vocabulary is the fallback.

Technical terms are mis-transcribed

Add the offending library, framework, or API names to your custom vocabulary. General-purpose speech models don't know "Zod" or "Drizzle" until you tell them.

Cursor's native voice sends empty or wrong prompts

Users have reported the native voice mode mis-firing on submit keywords and sending empty messages. If you hit this, switch to a system-wide dictation tool for prompt entry — you keep voice input without the agent-prompt-only constraints.

Dictation feels slow

On-device transcription uses the Neural Engine, which is shared with other apps. Close memory-heavy apps, or choose a smaller local model if your Mac has 8 GB of RAM. Transcription is noticeably faster on Apple Silicon than on older hardware.

Four practical options for voice in Cursor, with the trade-off that matters for each:

• Voibe — system-wide and on-device, with Developer Mode workspace resolution and custom vocabulary. Works in every Cursor surface and every other app; audio never leaves your Mac. $149 lifetime or $7.50/month, 7-day free trial, no account. Best fit for daily coding-by-voice on Mac. See our best dictation software for developers guide.
• Apple Dictation — free and built into macOS. Fine for occasional use, but it has a session timeout, no custom vocabulary, and no workspace awareness, so technical identifiers need manual fixing.
• Wispr Flow — polished cloud dictation with AI formatting, cross-platform. Capable, but it is cloud-based, so weigh that against dictating proprietary code. $144/year.
• Superwhisper — on-device Whisper modes plus optional cloud LLM cleanup and a flexible per-app mode system. $249.99 lifetime. A strong on-device alternative without dedicated IDE file resolution.
• Cursor native voice — built in and convenient for quick Agent prompts; scoped to the prompt, with the processing-location and reliability caveats above.

Using VS Code rather than the AI-first Cursor? See our companion how to dictate in VS Code guide, which covers Microsoft's on-device VS Code Speech extension. For the broader picture of on-device versus cloud dictation, see our cloud vs local dictation guide and offline dictation privacy on Mac.

Basics

Can you dictate in Cursor?
Yes. Cursor 2.0 has a native voice mode that fills the Agent prompt, and any system-wide Mac dictation tool types into every Cursor surface — the prompt, Cmd+K, chat, the editor, and the terminal.

Does Cursor have built-in voice input?
Yes, since Cursor 2.0. You hold to speak and the transcript drops into the Agent input. It is scoped mainly to that prompt and does not support @-mentions or model switching by voice, and Cursor has not documented whether transcription is on-device or cloud-based.

Setup

How do I dictate code and comments in the editor?
Use a system-wide tool (Cursor's native voice targets the Agent prompt, not the editor). Put your cursor in the file, hold your hotkey, and speak — comments, docstrings, and Markdown all work, and Developer Mode resolves file names you mention.

What is Developer Mode?
A Voibe setting that detects your open Cursor or VS Code workspace and resolves spoken file names, folder names, and project terms to their exact spelling — so "user service" becomes userService.ts automatically.

Privacy

Is voice dictation safe on a proprietary codebase?
Only if audio is processed on-device. Cloud tools transmit your voice — including file and function names — to a server. On-device tools like Voibe run the model locally so nothing leaves your Mac and dictation works offline.

Workflow

How should I voice-prompt the Agent and Composer?
Speak in short, structured chunks: goal, files, constraints. Use the Five-Part Voice Prompt framework for a repeatable structure, and a system-wide tool so you can dictate the same way into Cmd+K and the editor.

Dictating in Cursor turns the slowest part of AI coding — typing out what you want — into the fastest. Set up a system-wide on-device tool, enable Developer Mode so your file names resolve, and dictate your Cmd+K edits, Composer changes, Agent tasks, comments, and commit messages. Cursor's native voice is a fine shortcut for quick agent prompts, but a system-wide tool covers every surface and keeps your code on your machine.

Voibe is the Mac-native, on-device option built for exactly this: download it free (7-day trial, no account), enable Developer Mode, and dictate your next Composer prompt instead of typing it.

Keep going:

• How to voice-prompt ChatGPT, Claude, and Cursor — the Five-Part Voice Prompt framework
• The voice input workflow — the Talk-Draft-Polish loop for developers and writers
• Best dictation software for developers — the full buyer's view
• Getting started with Voibe — complete setup guide
• Speech to text on Mac — the category overview