The bug report that shows the bug.

how to report a bug with a screenshot

1. 1

   Press Alt+ `

   Drag over the broken part — the error message, the misaligned panel, the wrong total. Recording starts as you drag.

2. 2

   Narrate while you mark

   Arrow the button you pressed, box the message that came back — and say what you did and what you expected instead. The steps get spoken, not typed.

3. 3

   Paste it where bugs live

   The tracker, the team chat, an email to the vendor — the annotated screenshot and your transcribed report land together, in one paste.

your spoken steps arrive written out

Nothing to transcribe afterwards: what you said becomes ordinary editable text — read it over, add the version number, fix a word, then submit. And if it came out rambly, a voice mode can tidy the grammar and drop the filler before it lands — free on the built-in local model or your own Ollama server, and Pro can route it through your own OpenAI or Claude account.

not just for testers

QA files dozens a day, but everyone runs into things that are broken: the form that won't submit, the invoice that came out wrong, the page that renders scrambled. It's the same gesture whoever you are — crop it, say it, send it to whoever can fix it. And when a customer reports it first, support teams pass it along the same way.

real screens, real data — kept local

Bug screens are full of live data: accounts, orders, names. By default everything stays on your machine — your speech becomes text on your device, screenshots stay in a local folder, audio isn't uploaded to anyone, and the app tracks nothing about you. What reaches the tracker is exactly what you paste. The full network-use table →