Context lives in your head and on your screen, but tickets are blank text boxes. Translating what you just demonstrated into a written task is slow and lossy.
How it works
Record your screen
Show the work, the request or the change you want, and talk through it.
Add it to Agent Workstreams
Choose Add to Agent Workstreams on the What's next? step, or later from the recording.
Your dispatcher files it
Your dispatcher picks the repo and files a GitHub issue there, on the workstream the recording became.
- Turn a two-minute walkthrough into an issue someone else can pick up
- Keep the recording linked to every ticket
- Record asks for several projects in a row and let the dispatcher sort them
Making a ticket from video for someone else to pick up
This page is for the person asking for the change: product, support, design, or a founder clicking through the app. You record the ask and move on. You do not need to know which repo it belongs to.
Add the recording to Agent Workstreams
Connect GitHub and pick a default repository first. Then choose Add to Agent Workstreams on the card right after you record, on the recording's Agent tab, from its menu in your Library, or in the Chrome extension. The recording becomes one workstream in the Change request state, and sending it again opens that same workstream.
Not every ask needs a video. Choose New request at the top of Agent Workstreams, write what should change and choose Add to Agent Workstreams. Keep Let Vidmatic suggest and the dispatcher picks the repo.
Start the dispatcher
The dispatcher is a Claude Code session with the Vidmatic MCP server connected. Open Claude Code in one of your repo checkouts and run /loop 30m /mcp__vidmatic__auto-job-dispatcher. Every 30 minutes it picks up the workstreams still in the Change request state, reads each recording, works out the repo and has a helper agent file the issue by that repo's own rules. In the repo you run it from it also hands the ready issues to an orchestrator agent that builds and ships them.
To see what is waiting without claiming anything, run /mcp__vidmatic__auto-job-dispatcher --dry-run. A request waiting for a dispatcher that has not checked in recently shows the command to run, right after you file it and on its board.
Follow each ticket
Open Agent Workstreams in the sidebar. Each request is a row with a Change request chip until it is filed, then it shows its issue. When the dispatcher could not tell which repo the ask is for, the row reads Blocked: open it, choose Pick a repo, and it moves on. While no dispatcher runs, requests wait and nothing is lost.
Questions
- What does ticket from video mean here?
- You record your screen and talk through the change. The recording becomes a workstream, and your dispatcher files it as a GitHub issue in the repo it belongs to, with the recording linked.
- Which tracker does the ticket go to?
- GitHub only, in a repo your dispatcher can see from the folder it runs in.
- Do I need to know which repo it belongs to?
- No. The dispatcher picks the repo. When it cannot tell, the workstream reads Blocked, and you pick a repo on it.
- Will the dispatcher write the code as well?
- Only in the repo you run it in. Anywhere else it files the issue on the workstream, and building the change is a separate step someone starts in that repo.
- Can an agent add requests to Agent Workstreams?
- Yes. The enqueue_workstream_request tool on the Vidmatic MCP server adds a recording or a written request, for example from a voice assistant you dictate to.
Related use cases
- Screen Recording to GitHub Issue
Turn a screen recording into a GitHub issue your agent can build: numbered requirements tied to the moment you said them, grounded in your code.
- 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.
- Screen Recordings for Support Teams
Screen recordings for support tickets: capture the customer's issue and, with GitHub connected and auto-create on, escalate an issue with the video linked.
Stop Writing Tasks Manually
Record once. Vidmatic handles the documentation.
Explore more Vidmatic use cases
Docs: Agent Workstreams