Bug reports people can reproduce

"Steps to reproduce" written from memory are where bug reports go wrong. A recording made while you reproduce the bug can't skip a step, and your narration captures the context a form field never asks for.

The workflow

1. Record the window where the bug happens. A window recording keeps your other work out of the ticket.
2. Reproduce the bug, narrating as you go. Say what you're clicking, what you expected, and what actually happened.
3. Tidy the recording in the transcript. Delete the dead ends and false starts by deleting their sentences. Remove filler words in one click.
4. Attach it to the ticket. Export an MP4 for the bug tracker, or share an iCloud link the assignee can watch in the browser without an account. Paste the timestamped transcript into the ticket body so the report is searchable and skimmable.

Why recordings work better than written repros

• Steps can't be skipped. The video shows every click, including the one you didn't think mattered.
• Error text arrives exactly. There are no paraphrased error messages, because the dialog or console line is in the frame.
• Narration carries intent. "I expected this to stay disabled" is the difference between a bug and a misunderstanding, and it's 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

There is no proprietary viewer in the loop. An MP4 attaches to any tracker; an iCloud link plays in any browser; the transcript is plain text. Recordings of internal tools stay internal, because nothing uploads unless you share it.

To file the bug straight to a coding agent, see recording for coding agents.

Video

This page's video shows the workflow end to end. The steps it records are written up in the bug-reports video script.