QA spends as much time documenting defects as finding them. Reproduction steps get lost, screenshots go stale, and developers bounce tickets back for missing detail.
How it works
Record the repro
Record the failing flow and narrate the expected behavior.
Vidmatic transcribes it
Your voice becomes a transcript. In the recorder, choose Link to recording, Full transcription or both for the issue.
Defect is logged
The GitHub issue opens in your default repository with your labels, your assignees and a link to the recording.
- More of your testing time goes to testing
- Developers watch the failure instead of rebuilding it from notes
- Every defect uses the same issue layout, whoever filed it
Using an AI screen recorder for QA, one defect at a time
Set it up once
Go to Settings → GitHub, press Connect GitHub, and pick the repositories Vidmatic may open issues in. Choose a default repository and pin the others you test against. Each repository keeps its own default labels and assignees. With no labels set, the issue type decides: bug or enhancement.
Record the failing run
Start a recording from the Vidmatic Chrome extension and turn on Auto-create GitHub issue. Say the expected result out loud before the step that fails, then circle the wrong value or write the right one by hand. Each mark is saved as an image at the moment you confirm it.
Without the extension, press New Recording in the app and pick a screen or window, which also covers a desktop build. There is no pen in that mode, so name the element out loud and pause on it for a second.
To share only the failing moment in a chat thread, open the recording and cut a clip or a GIF. Clips and GIFs never count toward your plan's recording limit, and the original recording is never changed.
What the developer gets
When you stop, Vidmatic transcribes your voice and opens one issue in your default repository, with that repository's default labels and assignees. The link it adds is a share link, so anyone who can read the issue can watch the run, signed in or not. Pick Full transcription in the recorder to include every word you said. A developer with Claude Code can hand the same recording to their agent, which reads the timed transcript, every mark and an image of each mark with the code open.
Check the fix
If the developer's agent ran /mcp__vidmatic__before_after before with the issue URL, then after once the fix landed, Vidmatic pairs the two halves so they play back to back. The before half shows the bug, and the after half follows the same path on the fixed build, so you can check it without setting up the build yourself.
Questions
- Can QA use it without a coding agent?
- Yes. The GitHub integration opens the issue when you stop recording, with no agent involved. Agents are only needed for the skills that read recordings or record demos.
- Which tracker does it file into?
- GitHub. Vidmatic opens issues in the repositories you pick when you connect GitHub.
- Do testers need to install anything?
- Install the Chrome extension to draw on the page. Without it, New Recording in the app records any screen or window from the browser, with no pen.
- What if the tester did not say anything?
- Narrate while you test. The transcript is what carries the detail into the issue, and a plain recording with no pen has only your words to name the element. Without them, the developer gets the video and nothing more.
- Can I send just the part that fails?
- Yes. Cut a clip, or a GIF of the failing moment, from the recording. Both are saved as separate files next to the original.
Related use cases
- Bug Reports From Video
Make a bug report from video: record the bug and talk it through. With GitHub connected and auto-create on, Vidmatic opens the issue; or hand it to your agent.
- Generate a Demo Video
Finish a feature in Claude Code and let it record, narrate and publish the demo. Vidmatic drives your running app, adds a voice-over and returns a share link.
- AI Agent Proof-of-Work Demos
Proof of work for AI coding agents: when your agent says done, Claude Code records your running app and narrates the change, so you can see it before you merge.
Stop Writing Tasks Manually
Record once. Vidmatic handles the documentation.
Explore more Vidmatic use cases
Docs: GitHub integration