Development
Describe the bug properly the first time
The prompts that get good results from Cursor are the ones with reproduction steps in them, and those are precisely the prompts nobody enjoys typing.
Free tier runs on-device. macOS 14+ on Apple Silicon or Intel.
Workflow
What to use voice for in Cursor
- Bug reports in the chat pane with the exact steps, the expected result and what you actually got
- Composer instructions that name the files to touch and, as importantly, the ones to leave alone
- Inline edit requests where you say the intent rather than describing the diff
- PR descriptions written while the change is still fresh, before you have context-switched
- Commit messages that explain why, at the point where you would normally type "fix"
Friction
Where typing slows Cursor down
- Reproduction steps are boring to type, so they get shortened to "it breaks sometimes" and the model guesses
- Naming the constraint — do not refactor the auth layer — is an extra sentence, and extra sentences get dropped
- Every prompt takes your hands off the code you were just reading
- PR descriptions get written last, when you have already forgotten which decision was deliberate
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.
“The date picker returns the wrong day for anyone east of UTC. To reproduce: set the system timezone to Asia slash Tokyo, open the booking form, choose the fourteenth of March, and submit. The payload contains the thirteenth. I think it is the toISOString call in format dash date dot ts, around line sixty.”
“In the checkout flow, pull the Stripe client out of the component and into a hook, add a loading state while the payment intent is being created, and keep the existing error toast exactly as it is. Do not touch anything under the webhooks directory.”
“This is branch fix slash timezone off by one. It switches date formatting to the user's locale instead of UTC, adds three tests around the midnight boundary, and leaves the booking API untouched. Reviewers should look closely at the migration in schedule dot ts, because it rewrites existing rows.”
Hands stay on the problem, not on the prompt
Two things happen when you describe a change to Cursor by voice. The obvious one is that the description gets longer and more specific, which is the whole game with an agentic editor: the difference between a useful diff and a wasted one is usually three sentences of scope you did not bother to type. The less obvious one is that you can keep reading the code while you say them.
Hyprcore does not integrate with Cursor and does not need to. A keyboard shortcut starts dictation and text goes into whatever has focus, which might be Composer, the inline edit box, the chat pane, a commit message field in the source control panel, or the terminal at the bottom of the window. The same shortcut works in the GitHub tab where you are writing the PR body.
One honest limitation: this is dictation, not a code-by-voice system. Speaking symbols, brackets and camel case is slower and more error-prone than typing them, so the useful territory is prose about code, not code itself. Custom vocabulary helps with the names that recur, so your library names, service names and branch prefixes come out right instead of phonetically.
Frequently asked questions
Does it work in Composer, inline edit and the chat pane?
All three, plus the terminal and the commit message box, because none of them are special to Hyprcore. It types at the cursor, so any field in Cursor that accepts a keystroke accepts dictation. There is no extension to install in the editor.
Can I dictate actual code?
You can, but it is rarely worth it. Punctuation-heavy code comes out slower by voice than by keyboard and needs correcting afterwards. The gain is in describing what you want and why, and letting the editor produce the code.
Will it get branch names, package names and error strings right?
Common ones, yes; unusual ones, only after you teach it. Custom vocabulary takes your repo names, internal service names and acronyms and biases transcription towards them, which is the difference between "pnpm" and "pee en pee em" appearing in your prompt.
Does its shortcut clash with Cursor's own keybindings?
It might, since Cursor uses a lot of them. Hyprcore's dictation shortcut and its separate Action Mode shortcut are both remappable, so the usual fix is to move Hyprcore's rather than Cursor's.
Dictate somewhere else
Last reviewed July 25, 2026.
Try it
Talk into Cursor.
Free tier transcribes on-device on your Mac — no credit card required.
Native macOS · On-device dictation · No credit card