Development
Dictate the writing that surrounds your code
Nobody should be saying "open curly brace" out loud. The writing around the code is a different question, and there is far more of it than most of us admit.
Free tier runs on-device. macOS 14+ on Apple Silicon or Intel.
Workflow
What to use voice for in VS Code
- Commit messages that explain why, rather than restating what the diff already shows
- Pull request descriptions carrying the context a reviewer needs: what moved, what to read first, what you left alone
- README and docs sections, where the work is explaining the thing to someone who has never seen it
- The comment above the function that does something surprising, and TODOs with a reason inside them
- Prompts in the chat panel, where describing the bug in five sentences beats describing it in one
Friction
Where typing slows VS Code down
- Commit messages shrink to "fix" because the useful version is four sentences of typing at the end of a long day
- Docs are the first thing dropped once the feature works and your head is already in the next one
- A thin PR description forces every reviewer to reconstruct your reasoning from the diff
- One-line bug descriptions get an AI assistant answering a different bug
Examples
Things you would actually say
Spoken out loud, at normal pace. The words below are the input, not the output — Hyprcore types them where your cursor already is.
“Fix race condition in session refresh. Two tabs refreshing at the same time could both write the token, and the loser overwrote the newer value, which logged people out roughly once a day. Adds a mutex around the write plus a test that runs both refreshes concurrently.”
“This splits the checkout reducer across three files with no behaviour change intended. Start with cart dot ts, that's where the real logic moved. Tests are deliberately untouched so the diff is easier to trust. Node twenty two is now required because of the structured clone usage.”
“The build passes locally but fails in CI with module not found for the config package. It started after I moved the workspace to pnpm nine. My guess is the symlink layout, but I want to rule out the Docker image caching an old node underscore modules first.”
Dictate the prose, type the syntax
Speaking code into VS Code is a bad idea and it is worth saying so plainly rather than selling you the demo. Identifiers, brackets, operators, and indentation all have to be spelled out, every one of them is a chance for the transcript to guess wrong, and you spend longer correcting than you ever saved. IntelliSense and snippets already make typing code fast. Leave that part alone.
What is left is bigger than it looks. Commit bodies, PR descriptions, README sections, design docs, issue replies, review comments, TODOs, and the increasingly long prompts you write in a chat panel are all ordinary English, and dictation holds up there. Custom vocabulary is what makes it survive a real repository, because you can teach it your package names, your service names, and the terms that transcribe badly by default.
Action Mode covers the tidying. Select a commit body that came out rambling, ask for it shorter, and what you selected comes back rewritten without your hands leaving the desk. Dictation reaches the integrated terminal too, since that is one more place a cursor sits, though a command full of flags and paths is still faster from the keyboard.
Frequently asked questions
Should I dictate actual code with this?
No. Punctuation-dense syntax is the worst case for any speech model, and correcting a mis-transcribed identifier costs more than typing the line would have. Use it for the prose: commits, docs, comments, descriptions, prompts.
Does it work in the terminal, the command palette, and extension input boxes?
It types at the cursor, so all of those receive text, including the source control message box and the chat panel. Shell commands are the one place we would steer you back to the keyboard, because flags and file paths do not survive dictation gracefully.
Will it recognise technical vocabulary?
Once you have taught it. Add package names, acronyms, and internal service names to custom vocabulary and the bias applies whether you are running the local model or a cloud one, so pnpm, Postgres, and your own codenames stop arriving as approximations.
Is there a VS Code extension to install?
No, and there is nothing to set up per editor. Text goes to whichever field holds the cursor, which means forks such as Cursor and any other editor on the same Mac behave identically. Hyprcore is a macOS app, so none of this exists on Windows or Linux.
Dictate somewhere else
Last reviewed July 25, 2026.
Try it
Talk into VS Code.
Free tier transcribes on-device on your Mac — no credit card required.
Native macOS · On-device dictation · No credit card