Bug reports people can reproduce

Steps to reproduce written from memory leave out steps and paraphrase errors. A recording made while you reproduce the bug includes every step, and your narration includes context the ticket form does not ask for.

The workflow

1. Record the window where the bug happens. A window recording keeps your other windows out of the recording.
2. Reproduce the bug, narrating as you go. Say what you are clicking, what you expected, and what happened.
3. Tidy the recording in the transcript. Delete the wrong steps and false starts by deleting their sentences. Review and remove filler words together.
4. Attach it to the ticket. Export an MP4 and drag it into the bug tracker, or click Share and send it to the assignee with Messages, Mail, or AirDrop. Paste the timestamped transcript into the ticket body so the report is searchable and skimmable.

Why recordings work better than written repros

• Steps are all there. The video shows every click, including the one you did not think mattered.
• The error text is exact. The dialog or console line is in the frame, so there is no paraphrased error message.
• Narration states intent. "I expected this to stay disabled" tells the reader whether this is a bug or a misunderstanding, and it is natural to say out loud.
• The transcript makes it searchable. Six months later, the ticket is findable by what you said in it.

Works with any tracker

No proprietary viewer is involved. An MP4 attaches to any tracker and plays in any browser, and the transcript is plain text. Recordings of internal tools stay internal, because nothing leaves your Mac until you send it.

To send the bug directly to a coding agent, see recording for coding agents.