Say it out loud,and the ticket is filed
The best description of a bug is the one you give thirty seconds after seeing it, out loud, before it shrinks into a one-line note you cannot decode on Thursday. Khint lets a workflow listen on its own shortcut: hold the key, describe what happened, and what you said comes back as a structured Jira issue that is already filed.
You saw it clearly.
You will write it vaguely
Between noticing something and typing it into the tracker sits a detour: another app, another form, a summary field you fill in when the detail has already faded. Most of us leave a note instead, and the note is what the developer gets. Khint closes that gap with a voice key that runs a whole workflow: you describe the problem the way you would tell a teammate, and the shaping and the filing happen without you touching a keyboard.
The real voice run: the mic opens on a press, the level meter moves while you speak, and the words land at the caret in the Jira description field.
Spoken, shaped, filed
Reporting a checkout bug you just reproduced, without opening the tracker.
Give the workflow a key that listens
In Workflows, set Starts from to Voice and record a shortcut. A voice workflow has no palette row on purpose: its own combo is the microphone, which is why the editor asks for one before it will save. Pick something you can hit without looking, because that is the whole point of the flow.
Hold the key and describe it in sentences
One gesture covers both habits: a short press latches the mic open until you press again, and a longer press is a hold that ends when you let go. Speak the way you would to a teammate, symptom, what you clicked, what you expected. You are not filling a form, so nothing is lost by saying too much. See how voice works.
Let it get your nouns right
Generic dictation guesses at the words that matter most in a ticket. Khint primes the recognizer with the names of the agents and workflows in your active pack, so ticket keys, product terms and project names come out spelled the way you mean them. Fillers and punctuation are cleaned inside the same pass, so the text the workflow receives already reads like writing.
The agent step turns speech into a ticket
Your transcript is the workflow's running text, and the first step is an agent that reshapes it: a summary line a developer can scan, steps to reproduce, expected against actual, the impact and the environment. Save that prompt once as an Action and every spoken report comes out in the same shape. No prompt written yet? Type a one-line description in the editor and press Generate.
The Jira step files it and hands back the key
Connect Atlassian once on the integrations page and add a Jira Create issuestep at the end of the workflow. It carries the project you chose when you saved it, so a hands-free run never stops to ask. The created issue key comes back as the run's result, and if a Memory session is active the entry is logged after the write has landed, so the key sits next to what you said.
From your voice to the tracker
Up to five steps in series, starting from speech and ending in the tool.
Each step reads the result of the one before it, so the second agent works on the drafted ticket rather than on the raw transcript, and the Jira step files what survived both passes. Swap the middle step for what your team argues about: a severity call, a duplicate check against the terms you use, or a translation pass when the tracker is in English and the reporter is not.
Two ways to file what you just saw
Same observation, different amount of it left by the time it reaches the board.
Writing it up later
You jot a reminder, finish what you were doing, and come back to it after lunch.
- The reminder is four words and you no longer remember the fifth
- The steps to reproduce get compressed into one that does not reproduce
- The ticket gets bounced back with a question you could have answered live
- Filing it means leaving the app you were in, twice
Saying it now
You hold the shortcut where you are standing and describe it while it is still on screen.
- You speak for forty seconds and keep the detail a summary field would have eaten
- The agent step imposes your team's ticket shape, every time
- The issue is created in the project you configured, and the key comes back
- Your hands never leave what you were doing
What the listening key will not do
Voice is the one input that could be creepy, so the boundaries are part of the feature.
It does not listen in the background
The mic opens on your press and closes on the next press or when you let go. There is no always-on recorder, no bot joining the call, and no listening window you forgot you left open.
It does not invent words out of silence
A take with no speech in it is refused rather than sent. Recognizers answer silence with their most frequent filler, and that would reach you as your own words. If macOS has not granted the microphone, this is what you see instead of a plausible sentence.
It does not write while your back is turned
If a take ends because something interrupted it, the text goes to your clipboard only. No unattended paste into the app you were in, no agent run, no ticket filed on a recording you did not finish.
It does not pick the destination itself
The project is the one you set on the workflow's Jira step when you saved it, and a run performs that one write. Nothing is filed anywhere you did not configure in advance.
Why not just use system dictation?
You can, and you will get raw words at the cursor: yours to shape, copy, and carry into the tracker yourself. The difference here is what the transcript is for. It is not the output, it is the input of a saved workflow, so the same key that heard you also applies your ticket format and performs the write. If plain words at the cursor is all you want, Khint does that too, on a separate shortcut: voice dictation for product owners.
Common questions
Can I really create a Jira ticket by voice?
Yes. In Khint you build a workflow, set its Starts from to Voice, give it a keyboard shortcut, and end it with a Jira Create issue step. Holding that shortcut opens the microphone; what you say becomes the workflow's input, an AI agent step reshapes it into your team's ticket format, and the Jira step files the issue in the project you configured. The created issue key comes back as the result of the run, so you know it landed.
Do I have to hold the key down the whole time I speak?
Only if you want to. The same key supports both gestures: a short press latches the microphone open until you press it again, which suits a long description, and a longer press is a hold that ends the moment you let go, which suits a quick one. You do not choose a mode anywhere, the length of the press decides.
Will it get ticket keys and product names right?
Khint primes the recognizer with the names of the agents and workflows in your active pack, so the proper nouns that actually appear in your work are the ones it expects: ticket key prefixes, product terms, project names. Fillers and punctuation are fixed in the same pass, so the text handed to the agent step already reads like something written rather than something said.
Is Khint recording my meetings?
No. There is no recording bot and no always-on listener. The microphone opens when you press the shortcut and closes on the next press or when you release it, and a take with no speech in it is refused rather than transcribed. If a take is interrupted, the text goes to your clipboard only: it is never pasted unattended and never files a ticket on its own.
Where does the audio go, and what does a run cost?
The take is captured on your Mac and sent to Khint's transcription service; what comes back is text, and that text is what the workflow runs on. The cleanup pass runs inside the same request rather than as a second billed call, so one dictation costs one action's worth of credits. If a Memory session is active, the entry logged after the ticket is created lives in a local database on your machine.
File the next one before you sit down
Free with 300 credits a month, about 10 AI actions a day. No credit card. Record the shortcut once and the ticket is a held key away.