Agent Workstreams
Agent Workstreams is a coding agent dashboard: each issue your agent works on is a card with a box per stage, from the recording to issue step to the demo. Your agent reports each stage as it finishes.
What the coding agent dashboard shows
Each issue is a card with a box per stage, such as plan, build, review and ship. When a stage fans out, for example two reviewers checking the same change, each one appears as its own card under that stage. Open a card to read its record: a one-line summary, what it did, the decisions and findings it logged, the files it touched, and its links.
When the issue ships, the card shows the pull request and the demo video.
Where to find it
Open Agent Workstreams in the app sidebar. The list has one row per workstream with its status, and each row opens a page with its cards. A row marked Stalled has had no report from your agent for an hour; its stage card offers a prompt you can paste to your agent to pick the work up again.
The page is a view of what your agent reported. While the list is empty you can start a workstream from a GitHub issue URL. A stalled or paused row offers Ask your agent, and its stage card has the prompt that resumes it. Delete this workstream is on the workstream's own page. Your agent writes how each issue ends.
How it gets there
When your agent runs the prompt from Give to your agent on a recording, it starts a workstream for you. The skills that do work report as they go. If you drive the work your own way, run:
/mcp__vidmatic__workstream <issue URL>It opens a workstream for that issue and reports each stage through one call, report_phase. Your agent can read a workstream back with get_workstream, and list yours with list_workstreams.
Recordings you send to the change request queue usually get a board too: your watcher agent files each one as an issue and opens its board when your plan has room. The queue itself is under Change requests on the same page.
What the record is
The record is what your agent wrote, and Vidmatic only draws it. Vidmatic has no other view of what your agent does. Reporting never blocks the work: if a report fails, the agent keeps going and says so.
Stuck boards
/mcp__vidmatic__workstreams goes through every stalled, blocked or paused workstream, checks what is true on GitHub and in the code, and moves each one forward or closes it with an honest outcome.