Before
You type your AI prompts at typing speed. The prompts are shorter than they should be because each character is a wrist-cost. The commit messages are 'wip' or 'fix' because the source-control panel is one more place to type.
Cursor and VS Code users
Dictation in Cursor and VS Code
Your editor is your home base. The AI prompts and the prose around the code both happen inside it. Voiacast types into the editor on key release, into the prompt field, into the inline comment, into the source-control message panel — whichever one your cursor is in.
After
You hold the hotkey, you talk the prompt out loud, it appears in the prompt field. The commit message becomes one sentence about why. The inline comments capture the reasoning that would otherwise live only in your head.
Jobs to be done
What this scenario is for.
- Type AI prompts at the cadence you think, not at the cadence you type.
- Write commit messages and PR descriptions inside the editor's source-control panel.
- Dictate inline code comments without breaking flow.
- Reply to inline GitHub PR comments from the editor.
How to
Step by step.
- Pick a hotkey that doesn't fight the editor. Both Cursor and VS Code use Option-Space as a built-in shortcut in some setups. If the default conflicts, bind Voiacast to hold-Control-Space or hold-Option-` instead.
- Use it in the AI prompt field. Place the cursor in the AI prompt input, hold the hotkey, and talk through the change you want. The prompt arrives as if typed. Editing afterwards is the same as editing any typed prompt.
- Use it in the source-control message panel. Focus the commit-message textarea, hold the hotkey, dictate the message. The convention is to keep the first line a short imperative and use the body for the why; dictation makes the body the cheap path.
- Use it in inline comments. Click into an inline GitHub PR comment in the editor's review surface, hold the hotkey, dictate the comment. The dictionary handles your team's jargon on the fly.
Frequently asked
Questions, answered briefly.
Will Voiacast work in Cursor's AI chat?
Yes. Voiacast types into whichever text input has focus, including the AI chat input. The Whisper family of models handles long, exploratory prompts well.
Does it work in VS Code remote/SSH sessions?
Yes. Voiacast types into the local editor window; the editor handles the round-trip to the remote workspace itself. No special setup.
Will the dictionary correct technical terms inside prompts?
Yes. The dictionary runs on every transcription regardless of which app or text field is focused. Names like Next.js and Kubernetes spell the way you spell them.
Can I dictate code with it inside the editor?
Sort of. Prose around code is the right job. Identifiers, brackets, and shell commands are still faster on the keyboard.
Does it conflict with VS Code's built-in 'Speech' feature?
They are separate features. VS Code's Speech surface is editor-internal; Voiacast is system-wide and types into any focused field. If both are active they will both fire on overlapping hotkeys — bind one of them away from the conflict.