Skip to content

Show your coding agent what happened

A recording shows more of a UI bug than a typed description does. It shows what you clicked, what broke, and what the error said, and the transcript records your narration word for word.

  • Record the repro once, narrating as you go
  • Copy the transcript with timestamps in one click
  • Paste the clip into Claude Code, Cursor, or any agent chat

What a typed repro loses

An agent fixing a UI bug needs the same things a teammate would. It needs the exact steps, the exact error text, and the context you would say out loud. Typing that into a prompt loses information at each step. You paraphrase the error, forget a step, and leave out the aside ("it only happens when the cart has a subscription item") that identifies the bug.

The workflow

  1. Start a recording of the window where the bug happens.
  2. Reproduce it once, narrating as you go. Say what you are doing and what you expected. Stumbles are fine. You can cut them from the transcript afterward.
  3. Stop. Transcription ran on your Mac while you recorded, so the editor opens with the transcript in place.
  4. Copy the transcript with timestamps in one click, and export the clip as an MP4.
  5. Paste both into the agent chat. The transcript gives the agent your narration as text it can reason over, keyed to timestamps in the video, as in this example.
> fix the checkout crash, recording attached

00:04  I add the discount code and press Pay.
00:09  The button spins forever, and the console shows a 500
       from /api/checkout.
00:17  It only happens when the cart has a subscription item.

Why this fits agent workflows

  • The transcript is text. Agents read it directly, with no audio extraction step, and your steps arrive word for word.
  • Timestamps point into the video. An agent or a teammate can jump to 00:09 and read the console frame.
  • No upload service is involved. The MP4 is a local file when you stop recording. Nothing from your codebase or your screen passes through a third-party video host.
  • Works offline. Recording and transcription run on your Mac, so the workflow is the same on a plane or an air-gapped network.

The same clip works for people

The same clip goes into a pull request, a bug tracker, or Slack. For issues a person will triage first, see bug reports and QA.