Vibe coding flips the job. You describe what you want, the AI writes the code, and you steer. Cursor, Claude Code, Windsurf and Copilot are all very good at the writing part. The weak link is usually the description.
Typed instructions come out thin. "Fix the login bug." "Make the button work." The agent guesses, edits the wrong file, and you spend the next ten minutes undoing it. The fix is not a better model. It is a better brief, and the fastest way to give a better brief is to say it out loud.
You are not dictating code. You are dictating intent. Speak what is wrong, what should happen and where to look. Let the AI write the syntax.
Why Voice Fits Vibe Coding
An instruction to an AI coding agent is prose, not code. It reads like a bug report or a ticket. That is exactly the kind of writing voice is best at.
You speak at roughly 150 words per minute and type at about 40. A solid 200 word instruction takes about 80 seconds to say and 5 minutes to type. In practice, nobody types 200 words into an agent panel. They type 20 and hope.
Agents reward detail. When you name the file, describe the expected behaviour and mention what you already tried, the first attempt lands far more often. Voice makes that detail cheap.
Setting It Up in Each Tool
TAWK is a menu bar app for Mac. Hold a key, speak, release, and the text is typed at your cursor. Because it types like a keyboard, it works in every editor and terminal without a plugin.
Cursor
Open the chat or agent panel and click into the input. Hold your key, describe the change, release. Read it, then send. Use Cursor's own file mentions to attach the exact files. More detail on the Cursor voice to text page.
VS Code
Copilot Chat, Claude extensions, any AI panel with a text box. Click in, hold, talk. It also works in the source control box for commit messages. See voice to text for VS Code.
Claude Code in the Terminal
Start Claude Code in Terminal, iTerm2 or the terminal panel inside your editor. With the cursor at the prompt, hold your key, speak the instruction, release. The words are typed into the prompt. Read them over, then press Enter yourself. Long spoken instructions work well here, because Claude Code is built for multi step tasks across a whole project.
Windsurf
Click into the Cascade panel and talk. Same flow as everywhere else.
The Spoken Instruction That Works
Every good instruction to a coding agent has the same four parts. Say them in this order and your hit rate goes up fast.
- The bug or the goal. What is happening now, in plain words.
- The expected result. What should happen instead. Be concrete.
- The files. Where the problem lives, or where the new code should go.
- The limits. What not to touch. Style rules. Libraries to avoid.
"When a user logs in with Google and their email is not verified yet, the app sends them to the dashboard and then crashes because the profile is empty. It should send them to the verify email screen instead. The redirect logic is in the auth callback route and the profile loading is in the dashboard layout. Do not change the email login flow, that one works. Add a check in the callback and write one test for the unverified case."
That took about 25 seconds to say. It names the bug, the expected behaviour, two locations and a clear boundary. Typed, it would most likely have been "fix google login crash".
A Practical Voice Workflow
1. Plan Out Loud First
For anything bigger than a small fix, ask for a plan before code. "Before you write anything, tell me which files you would change and why." Then read the plan and talk back: "Good, but skip the database change, we can do that in the API layer." Plans are cheap to correct. Code is not.
2. Describe the Bug Like a Ticket
Say the steps to reproduce, what you saw and what you expected. If there is an error message, paste it. Do not read a stack trace aloud.
3. Name the Files
Say the file or folder names in plain words, then use your editor's file attach feature for the exact paths. Spoken file names with odd casing can come out slightly wrong, and a wrong path sends the agent to the wrong place.
4. Review the Diff by Reading
This is the step people skip. When the agent finishes, stop talking and read every changed file. Look for removed checks, renamed functions and edits outside the area you asked about. Voice makes instructions fast, which makes it tempting to accept fast. Do not.
5. Talk Back With One Clear Correction
Once you have read the diff, give all your feedback in one go. "In the callback you removed the null check on the session, put that back. The test is good. Rename the helper to something that says what it checks." One clear message beats five small ones.
Hands Free Mode for Big Features
Starting a new feature deserves a proper spec. Double tap your TAWK key to start hands free mode, then walk through the whole thing: who it is for, what the screens do, the edge cases, what done looks like. Tap once to stop.
It stops by itself after a minute of silence, and one session can run up to 15 minutes. Dictations over 2 minutes are written in pieces at natural pauses, so nothing is cut. Three minutes of talking gives you roughly 450 words of spec, which is more than most tickets ever get.
Tip: dictate the spec into a markdown file in your project first, then point the agent at it. You keep the spec, and you can refine it between runs.
Download TAWK, open Cursor or Claude Code, hold your key and describe your next change. Works on macOS 11 and later, Intel and Apple Silicon. $59 once if you keep it.
5,000 words free • No card • No account
What Voice Is Bad At
Be honest about the limits and the workflow stays smooth.
- Exact syntax. Brackets, operators and regex are faster to type.
- Unusual identifiers. A name like useAuthV2Ctx will not come out right from speech. Type it, or attach the file.
- Error output. Paste it. Never read it aloud.
- Open plan offices. Talking to your editor all day in a quiet shared room is awkward. A headset mic and a lower voice go a long way.
The best setup is a mix. Speak the sentence, type or paste the exact bits. Most of an instruction is plain English, so most of it can be spoken.
Privacy for Proprietary Code
Your instructions often describe internal systems, unreleased features and client names. With TAWK, your voice and your words never leave your Mac. Transcription runs on your Mac with no internet, using OpenAI's Whisper speech model inside the app. The text then goes to your AI coding tool the same way typed text would, under whatever terms your team already accepted for that tool.
TAWK sends only a few anonymous usage counters and an optional daily health check, with no audio and no words, and you can switch those off in Settings > Privacy. More on how offline speech works in offline speech recognition and privacy.
Get Started
- Download TAWK. Every download includes 5,000 words free, no card.
- Pick a key that does not clash with your editor shortcuts.
- Open your agent panel or start Claude Code.
- Say the bug, the expected result, the files and the limits.
- Read the diff, then talk back with one clear correction.
The same setup handles the rest of your writing too: PR descriptions, reviews and Slack. See voice to text for developers for that side of the day.
Questions People Ask
What is vibe coding with your voice?
It means describing what you want built or fixed out loud, and letting an AI coding tool like Cursor, Claude Code or Windsurf write the code. You speak the intent, the bug and the files; the AI writes the code; you read the diff and talk back with corrections.
Does TAWK work with Claude Code in the terminal?
Yes. TAWK types at your cursor in any Mac app, including Terminal, iTerm2 and the terminal inside VS Code or Cursor. Start Claude Code, hold your key, speak your instruction, release, read it, and press Enter yourself.
Can I dictate actual code?
You can, but it is rarely worth it. Voice is great for intent: what should change, why, and where. Exact syntax, regex and unusual variable names are faster to type or paste. Speak the explanation and let the AI write the code.
Does it work in Cursor, VS Code and Windsurf?
Yes. There is no plugin to install. Click into the chat or agent panel in Cursor, Copilot Chat in VS Code, or Cascade in Windsurf, hold your key, and talk. TAWK types the words where your cursor is.