TL;DR
- Developers should dictate prose (PRs, tickets, prompts, Slack), not source code.
- System-wide paste matters: the hotkey has to work in Cursor, Linear, GitHub, and Terminal-adjacent tools.
- Voice is often the fastest way to dump context into an AI coding agent.
App pages: Voice writing in Cursor and voice prompting for ChatGPT.
AI dictation for developers is for the writing around the code: pull requests, tickets, design docs, Slack, and prompts into Cursor or ChatGPT. It is not a replacement for typing syntax. Used that way, voice is one of the highest-leverage habits you can add to a Mac engineering setup.
What to dictate (and what not to)
Dictate. PR summaries, review replies, RFC sections, incident notes, standup updates, and long agent prompts.
Type. Brackets, types, refactors, and anything where the keyboard’s precision beats speech.
If dictation is faster than typing for your prose, you will feel it on the third PR of the day, not in a hello-world file.
Cursor, VS Code, and the rest of the IDE
The requirement is system-wide paste. If dictation only works well in Notes, it will not survive a real stack. Lazur uses a hold-to-talk hotkey and pastes at the cursor in Cursor, VS Code, Xcode, and browser-based GitHub.
A useful prompt pattern, spoken:
“In
billing.ts, the webhook can double-charge if Stripe retries. Write a failing test and a guard that’s idempotent onevent.id. Don’t change the public API.”
That is voice writing aimed at an agent, not a transcript of your muttering.
Comments and commit messages
Speak the why: “Retry because the upstream 429s for 2 seconds; sleep with jitter.” Rewrite can turn that into a comment or a conventional commit body. Skip dictating feat: prefixes if you already have a template, add those with the keyboard.
Team norms
- Don’t dictate secrets. Treat the mic like a Slack channel.
- Add internal names (services, customers, acronyms) to a personal dictionary.
- Privacy: STT can be on-device; know when rewrite leaves the machine.
Next step
Tomorrow, write one PR description and one Cursor prompt by voice. If you still spend longer editing than speaking, you are using a transcriber. Download Lazur for Mac and run both in the apps you actually ship from.
FAQ
- Can developers use AI dictation to write code?
- You can dictate comments, commit messages, and prompts. Dictating raw syntax is usually slower than typing. The win is the written work around the code: PRs, RFCs, Slack, and agent prompts.
- Does Lazur work in Cursor and VS Code?
- Yes. Lazur is system-wide on macOS, so the same hotkey pastes at the cursor in Cursor, VS Code, Xcode, GitHub in the browser, Linear, and Slack.
- Is dictation useful for ChatGPT or Cursor prompts?
- Yes. Talking through the bug, the files involved, and the constraint often produces a better prompt than a short typed sentence. You review once, then run the agent.