For developers working with AI coding agents
Talk to your agent.Your code's names come out right.
The prompt you would never type because it is too long is the one that works.
Claude Code, Cursor and Codex do their best work from a full explanation: what you tried, what you suspect, what must not change. Typed, that becomes one line. Spoken, it takes thirty seconds, and the function names, libraries and file paths arrive spelled the way your code spells them.
Download for MacAccount first, then download. Free to start, no card. · See every profession
The real friction
“Dictation mangles code. It will write “use effect” and “post gress” and I will spend longer fixing it.”
That is what a general-purpose recogniser does, because it has never seen your codebase. VoiceCatalyst learns the terms from what you have already written and from what your agents write back, so the names in your project are names it knows.
You are not dictating code. You are dictating the reasoning around it — the part agents are worst at guessing and you are fastest at saying.
A longer, specific prompt costs you seconds to say and saves the three rounds of “no, not that” that a one-line prompt buys.
What actually happens
Be unpolished in private.Deliver clean text in public.
You said
the use effect in the settings panel fires twice on mount because the post gress listener re-subscribes, don't touch the reducer, just move the subscription into the provider and make sure the cleanup unsubscribes
VoiceCatalyst delivered
The useEffect in the settings panel fires twice on mount because the Postgres listener re-subscribes. Don't touch the reducer, just move the subscription into the provider and make sure the cleanup unsubscribes.
Your own words, with your project's names spelled as your code spells them. Recognition runs on your Mac.
Where it fits
High-value moments.
Prompts to coding agents
Give Claude Code or Cursor the whole picture: what broke, what you ruled out, what must stay. Better input, fewer rounds.
PR descriptions
Say what changed and why while the diff is still in your head, instead of writing “fixes bug”.
Design notes
Talk through the tradeoff out loud and keep the reasoning, not just the decision.
Review comments
Explain the concern properly, in a full sentence, rather than a terse note that starts a thread.
How it works
Three steps. One key.
Press a key. Speak.
One hotkey anywhere on your Mac. No app switching, no mode to remember.
It transcribes on device.
Your voice never leaves your machine. There is no cloud transcription path for it to leave through.
Your words land right.
The names and terms you actually use are already known, so the text arrives finished instead of needing repair.
Privacy
Your codebase's namesstay on your Mac.
Prompts describe unreleased code, internal systems and customer problems. Cloud dictation sends that audio to a vendor before it ever reaches your agent.
Recognition here happens on your machine. The vocabulary it learns from your code is yours, and we never pool it with anyone else's.