Screen Recording to GitHub Issue
Say what you want on screen. Your coding agent turns it into one GitHub issue with numbered requirements, grounded in your code.
- 1Connect Claude Code (once per machine)
claude mcp add --transport http --scope user vidmatic https://api.vidmatic.ai/mcpNo key in it: run /mcp, choose Authenticate, and sign in from your browser.
- 2Record your screen, then hand your agent the recording
/mcp__vidmatic__workstream_from_video <recording id>Use the id from your recording's link. Your agent reads it and files one GitHub issue.
How it works
1
Record the ask
Show the bug or the change and say what you want. Circle the parts that matter.
2
Your agent reads it with your code open
It reads the transcript and your marks, then finds the files they point at.
3
One grounded issue
It files exactly one GitHub issue: requirements R1 to Rn, each tied to what you said and to a file in your repo.
- Requirements come from your words, not a summary of them
- Every requirement points at real code
- The recording stays linked to the issue
Questions
- How do I turn a screen recording into a GitHub issue?
- Connect Claude Code to Vidmatic, record your screen, then run /mcp__vidmatic__workstream_from_video with the recording id. Your agent reads the recording and files one issue in your repo.
- Who writes the issue, Vidmatic or my agent?
- Your agent does, in your repo, with your code open. Vidmatic gives it the recording's transcript, marks and frames.
- What if someone else recorded it?
- A recording sent to you carries a watch token. Your agent passes it on every call and files the issue itself.
- Does it work with Jira or Linear?
- This loop files GitHub issues, in your repo, through your own agent.
Turn Your Next Recording Into an Issue
Connect Claude Code once, then hand it a recording.
Explore more Vidmatic use cases