Human review for agent-built UI

Ship a review artifact with every UI change.

FlowReview turns an agent’s Playwright flow into a video, timeline, screenshots, verifier report, and exact comments humans can send back.

RecordScrubCommentRepair
pricing-redesignfeature/pricing-ui · 2 recordings
verifier passed
click captured
landingpricing cardscheckout modal
00:12.4 / 00:30.1
ReplayLoom-like walkthrough
CommentsTimestamp + screen context
Verifier0 console errors
BranchPR-ready artifact links

Record the path

Agents write a Playwright flow for the UI they changed.

Upload the proof

Video, screenshots, DOM, logs, and report become one artifact.

Fix with context

Human comments export as exact agent-readable feedback.

Cloud beta

Projects, branches, recordings.

feature/pricing-uiPR #123
pricing-page.flow.jsPremium plans + checkout modal
passed
billing-settings.flow.js1 horizontal overflow warning
warning
Quick setup

Drop it into any frontend repo.

npm install -D flowreview npx flowreview init npx flowreview login --endpoint https://flowreview.stackonfire.com npx flowreview project create --repo owner/repo npx flowreview record --flow flows/pricing.flow.js --verify FLOWREVIEW_PROJECT_TOKEN=frp_... npx flowreview upload --branch feature/pricing npx flowreview comments --branch feature/pricing
The whole manual

Copy this into Claude, Codex, Cursor, or Windsurf.

Paste it into your agent rules so every UI task ends with a durable review artifact, branch index, and comment fetch loop.

AGENTS.md
You are working in a frontend repo with FlowReview.

When you change UI:
1. Create or update a focused flow in flows/*.flow.js for the changed path.
2. Start the dev server if it is not already running.
3. Run: npx flowreview record --flow flows/<name>.flow.js --verify
4. Fix any verifier issues and rerun until it passes.
5. Run: npx flowreview upload --branch "$(git branch --show-current)"
6. Return the FlowReview cloud artifact URL as visual proof for the reviewer.
7. If the reviewer leaves feedback, run: npx flowreview comments --branch "$(git branch --show-current)"
8. Read .flowreview/latest/review.md, fix open comments, rerun record + upload.

Requirements:
- FLOWREVIEW_PROJECT_TOKEN must be set (get it from the project's Tokens tab).
  Without it the upload will fail — ask the user to add it to their environment secrets.
- Record like a concise Loom walkthrough, not a Playwright trace.
- Use review.click(...) for visible user-triggered navigation and state changes.
- Use review.scrollTo(...) when moving through sections of a page.
- Use review.point(...) to call out important static evidence without clicking it.
- Keep raw page.goto, locator.click, locator.scrollIntoViewIfNeeded, and long waits out of the main review path unless they are hidden setup.

One-time project setup:
npx flowreview login --endpoint https://flowreview.stackonfire.com
npx flowreview project create --repo owner/repo

Do not ask the human to inspect screenshots in chat. Make the artifact.