A good bug report means typing out steps, attaching screenshots and explaining what went wrong. Most reports skip half of that, so the engineer asks "how do I reproduce this?" and the thread drags on.
How it works
Record the bug
Capture your screen, narrate what you did and what broke, and circle it with the pen.
It becomes an issue
With Auto-create GitHub issue on, Vidmatic opens one in your default repository. Or hand the recording to your coding agent.
The video stays attached
The issue links to the recording with a share link, so anyone who can read the issue can watch it.
- The report is what you showed and said, not a retyped summary of it
- Every report links back to the original video, and can carry the full transcript
- Engineers watch the bug instead of asking how to reproduce it
Writing a bug report from video, start to finish
Record it so the bug is obvious
Start on the page with the bug and say what you expect as you go. When it breaks, pick up the pen in the Vidmatic Chrome extension and circle the wrong value or cross out what should not be there. Each mark is saved as an image at the moment you confirm it, with the sentence you were saying. Without the extension, press New Recording in the app and name the element out loud.
Path one: Vidmatic opens the issue
Connect GitHub under Settings → GitHub and choose a default repository. In the recorder, turn on Auto-create GitHub issue, choose labels and assignees, and pick Link to recording, Full transcription or both.
When you stop, Vidmatic transcribes your voice and opens the issue in your default repository, with the labels and assignees you chose. The link it adds is a share link, so anyone who can read the issue can watch the recording, and with Full transcription on, every word you said is in the issue too. Vidmatic remembers your last choice for the next recording. Talk while you record: the transcript is what carries the detail.
Path two: your coding agent files it
Choose Give to your agent and paste the prompt into Claude Code. The agent reads the transcript and your marks, searches your code and files one issue with a row per ask, each anchored to a file and line. Then it starts on the fix. Ask it to run /mcp__vidmatic__before_after before it changes anything, so the fix ships with before and after video.
When someone else found the bug
Open their share link and use Give this to your agent. The prompt it copies includes --token, which lets your agent read that one recording.
Questions
- How do I make a bug report from a video?
- Record the bug with Vidmatic and narrate it. Either turn on Auto-create GitHub issue so Vidmatic opens the issue when you stop, or paste the Give to your agent prompt into Claude Code and let your agent file it.
- What goes into the issue?
- Through the GitHub integration: a share link to the recording, the full transcription if you chose it, and your default labels and assignees. Through your agent: a plain summary, a row per ask with the time, the mark, your words and file and line anchors, and acceptance checks.
- Does the issue include expected and actual behavior?
- Say both out loud while you record. The transcript carries them into the issue, and your agent quotes each ask with the moment you said it.
- Which tracker does it file into?
- GitHub only, through Vidmatic's GitHub integration or through your coding agent.
Related use cases
- AI Screen Recording for QA Teams
An AI screen recorder for QA. Record the failing run with the pen and your voice. With GitHub connected and auto-create on, the issue opens when you stop.
- Create a Ticket From a Video
Create a ticket from a video. Record your screen, add it to Agent Workstreams, and your dispatcher files a GitHub issue in the right repo.
- Screen Recording for AI Coding Agents
Screen recording for AI coding agents: record your screen, circle it and say it. Claude Code or Cursor reads the transcript, marks and frames over MCP.
Stop Writing Tasks Manually
Record once. Vidmatic handles the documentation.
Explore more Vidmatic use cases
Docs: Recording your screen