S Standupmate
Skip to content

Visual handoff for engineering and QA

Prove the feature works, without a single “can you screen-share?”

Standupmate sits between engineering and QA. Ship test suites with before/after screenshots, or attach a reel when video is the evidence — your agent drives both over MCP, and QA opens one link with no account.

MCP-native workflow · QA links you can expire · Playwright and CI attach when you need video.

Pro · EUR 15/month · webm, mp4, mov, gif and stills up to 200 MB.

Bulk archive keeps filter state

Approved
0:28
1:12
  • 0:03 Select 40 rows, hit Archive pass
  • 0:28 Filter still reads “Unreviewed” pass
  • 0:51 Undo restores all 40 rows pass

QA opens the same link on any machine, scrubs to a timecode, pins a note to that exact moment, and records the verdict your agent reads back.

One issue, end to end

Four calls, and the evidence is with QA

  1. Engineer + agent

    The feature is finished. Playwright, a CI job or the agent itself makes the recording.

  2. Standupmate

    One reel: the recording, steps pinned to timecodes, issue ref, branch, commit.

  3. QA, no account

    Opens the link on any machine, pins a note to the exact moment, records a verdict.

  4. Agent closes it

    The verdict and every note come back over MCP, with the embed to paste into the ticket.

Request changes sends it back instead: fix the feature, rotate the upload link, re-record, submit the same reel again. QA keeps the thread.

  1. 1

    create_reel

    Title, issue ref, branch, commit. The response carries the page URL, the QA link and a single-use upload command.

  2. 2

    Push the recording

    Playwright, a CI job or curl posts the raw bytes once. No long-lived secret ever leaves the runner.

  3. 3

    Mark the steps

    Every verified behaviour becomes a clickable timecode on the reel timeline, so QA jumps straight to the moment.

  4. 4

    Verdict flows back

    read_qa_feedback tells the agent whether it may close the issue, with every note attached.

Why not a folder of mp4s

The gap between “done” and “verified”

Built for the agent loop

Every reel is a REST resource and an MCP tool. Cursor, Claude Code or a CI job can create it, attach the recording, tag the steps and read the verdict without a human in the path.

QA never installs anything

The review page needs no account and no plugin. Timecodes are URL fragments, notes are pinned to the moment they describe, and the verdict is one click.

Evidence stays with the issue

Recordings are keyed to the issue ref, branch and commit, so six months later you can still show what shipped and who signed it off.

Getting media in

Three ways in, one place to review

Drag and drop
Drop a screen recording, a GIF or a screenshot onto the reel page. Good for manual QA and design reviews.
Playwright, CI, curl
The reporter turns a suite run into a reel; examples/ci/proofreel-attach.sh does it with plain curl. A one-shot token posts the file, so no long-lived secret leaves the runner:
curl -X POST --data-binary @recording.webm \
  -H "Content-Type: video/webm" \
  "https://standupmate.com/api/v1/reels/<id>/media?upload_token=…"
MCP tools
create_reel, add_step, submit_for_review and nine more, straight from the coding agent.

MCP config

{
  "mcpServers": {
    "standupmate": {
      "url": "https://standupmate.com/mcp",
      "headers": {
        "Authorization": "Bearer pr_your_key"
      }
    }
  }
}

Keys are hashed at rest and shown once. Rotate or revoke them from the dashboard, and every request is scoped to your workspace.

Close the loop on your next issue

Record one reel from your current branch and send QA the link. No install, no migration, no change to how you write the feature.