AI Agent Proof-of-Work Demos
Your agent says it is done. Make it show you: a narrated recording of the change, from your running app, before you merge.
- 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.
- 2Then, whenever your agent ships something
/mcp__vidmatic__record <what to show>Records your real UI, narrates it and puts the demo in your Inbox.
How it works
Your agent finishes
Run /mcp__vidmatic__record and name what to show. Run it bare and it lists what it could demo from your recent commits, then asks you to pick.
It records the real app
Playwright drives your running app through the change, in your actual UI.
Narrated proof
A voice-over timed to what is on screen. The demo lands in your Inbox, with a public link for the PR unless you made it private.
- See the change work before you merge it
- Reviewers watch two minutes instead of checking out a branch
- The demo matches the build, because it was recorded from it
What an AI agent proof-of-work demo looks like in practice
When to ask for one
Ask when your agent reports a change as done and you have not seen it run. Start your app's dev server and run /mcp__vidmatic__record with the feature named, for example /mcp__vidmatic__record the new checkout page. The agent learns the feature from the code, plans a path through it and records that path.
How the demo is made
The agent writes a script first, one line per moment. preflight_narration checks that each line fits its time slot, and a line that runs long is shortened before anything is recorded. Playwright then drives your app in a headless browser to fit the script. begin_upload sends the video, create_demo adds the script, and Vidmatic renders the voice-over. Nothing is encoded on your machine.
For a bug fix, film before and after
A fix is easier to trust when you have seen the bug. Run /mcp__vidmatic__before_after before with the issue URL before the agent touches the code, then the same command with after once the fix lands. The two halves stay separate recordings. Vidmatic pairs them so they play back to back.
Where the proof lands
Every demo lands in your Inbox, and the agent prints the Inbox link. Demos follow your default in Settings → Demo videos, which is public unless you changed it, so you also get a public link to paste into the pull request. Add --private to keep one demo to yourself. When the agent reports its work on Agent Workstreams, the shipped card shows the pull request and the demo video.
Questions
- What is a proof-of-work demo?
- A short narrated video of the change your coding agent made, recorded from your running app, so a reviewer can see it work before merging.
- Is the demo recorded from my real app?
- Yes. Playwright drives your running dev server; there are no mock screens or slides.
- Where does the video go?
- It lands in your Vidmatic Inbox. Demos are public unless you changed your default in Settings → Demo videos, so you also get a link you can paste into a PR, Slack or a release note.
- How is this different from generating a product demo?
- Same recorder, different reader: a proof-of-work demo is for the reviewer of one change, a product demo is for your users.
- Do I need ffmpeg or a screen recorder installed?
- No. Your machine needs Node and a headless browser, and the skill installs Playwright if it is missing. Vidmatic encodes the video and renders the voice-over.
Related use cases
- 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.
- 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.
- 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.
Make Your Agent Show Its Work
Connect once, then one command after every change.
Explore more Vidmatic use cases