Project management
Fill in the Linear description field for once
Linear makes creating an issue almost frictionless, which is why so many issues are a title and nothing else.
Free tier runs on-device. macOS 14+ on Apple Silicon or Intel.
Workflow
What to use voice for in Linear
- Descriptions with the repro, the expected behaviour and the actual behaviour, written while you still remember them
- Acceptance criteria as a numbered list, which is the format speech happens to be good at
- Triage notes explaining why something moved cycle, was closed, or is blocked and on what
- Comments that answer a question fully instead of promising to answer it later
- Project updates at the end of a week, when your appetite for writing is at its lowest
Friction
Where typing slows Linear down
- The title is quick and the description is not, so the description stays empty and the context lives in someone's memory
- Acceptance criteria require enumerating cases, and each extra case is another line of typing you can talk yourself out of
- Triage is a fast, repetitive pass, and typing an explanation breaks its rhythm
- Issues written thinly get reopened later for a conversation that should have happened once
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.
“Signups through an invite link fail when the workspace already has a pending seat request. Reproduced twice on staging this morning with a fresh Gmail address. Expected: the invite is accepted and the pending seat request clears. Actual: a five hundred from the seats endpoint, and the invite stays unused. Sentry event is tagged seats dash pending dash conflict.”
“Acceptance criteria. One: the export button is disabled while a job for that workspace is already running. Two: a completed export shows a download link that stays valid for seven days. Three: exports over fifty megabytes are emailed rather than downloaded in the browser. Four: we log the row count and the duration on every run, successful or not.”
“Moving this to next cycle. It is blocked on ENG four one two, the auth rewrite, which is not landing before Thursday at the earliest. I have set the estimate to three points and left it unassigned so triage can pick it up fresh on Monday.”
The description field is where issues quietly die
A Linear issue with only a title is a note to yourself that expires in about a week. Everyone knows this and everyone does it anyway, because the title takes four seconds and the description takes four minutes, and the four minutes arrive at exactly the moment you want to get back to what you were doing.
Speech changes the arithmetic rather than your discipline. Saying the repro steps and the expected behaviour costs about as long as thinking them, and the result is a description someone else can act on without booking time with you. Acceptance criteria are the strongest case: numbered lists dictate cleanly, because you already say them as "one, two, three" out loud.
Action Mode handles the tidy-up. Select a rambling description, say "Hyper, turn this into acceptance criteria," and the selection is rewritten in place. It applies equally to a comment you have over-explained, or a project update that needs cutting to half its length before anyone will read it.
Frequently asked questions
Can Hyprcore create a Linear issue for me?
No. There is no Linear integration, no API token and no bot. Hyprcore types into the field you have open, so you create the issue in Linear as usual and dictate the parts that are text: the title, the description, the comments.
Does it work in the Linear desktop app and in the browser?
Both, identically. The desktop app and a browser tab are the same thing from Hyprcore's point of view, which is a focused text field. That also covers the command menu's text inputs and the search box, though those are rarely worth dictating.
How do I get issue IDs and teammate names transcribed correctly?
Add them to custom vocabulary. Team prefixes like ENG or GROWTH, product codenames and colleagues' names are exactly the sort of thing generic models mangle, and the vocabulary bias applies whether you are running on-device transcription or the cloud option on Pro.
Is this useful for triage, or only for writing long issues?
Triage is arguably the better fit, because the bottleneck there is explaining decisions quickly. A one-sentence spoken comment about why something is deferred takes a couple of seconds and saves the question being asked again in the next planning session.
Dictate somewhere else
Last reviewed July 25, 2026.
Try it
Talk into Linear.
Free tier transcribes on-device on your Mac — no credit card required.
Native macOS · On-device dictation · No credit card