Run your end-to-end tests with Reflow. Give your coding agent snapshots it can use to check for regressions.
Review changed screenshots and business results in your pull request, with links to the original evidence.
Closed beta. Sign in to register interest; app access is limited to approved teams.
$ reflow apply customer → order → refund → verify ✓ Prepare the customer shop.customer id="alex" balance=100 CUSTOMER BALANCE INVENTORY Alex $100.00 10 available ✓ Place an order shop.place_order customer="alex" total=25 ORDER BALANCE INVENTORY paid $75.00 9 available ✓ Refund the order shop.refund_order customer="alex" ORDER paid → refunded BALANCE $75.00 → $100.00 INVENTORY 9 → 10 ✓ Assert the business outcome shop.expect_balance customer="alex" amount=100 shop.expect_stock count=10 shop.expect_order status="refunded" shop.snapshot name="after-refund" ✓ Balance restored ✓ Stock restored ✓ Order refunded snapshot: after-refund 4 flows passed. Snapshot ready for review.
Who can invite a teammate? What should a refund restore? Your agent records those rules in Reflow’s application knowledge repository and updates them as the app changes. It reads and writes that knowledge through MCP.
Each page connects that context to the flows that check it, so the next change starts with what your app is supposed to do.
Explore application knowledgeOwners can invite teammates as editors or viewers. Accepting an invitation must grant that role.
src/team/invitations.ts/settings/teamSelected role = accepted role
Expired invitations: coverage not recorded.
Apply the customer’s discount before payment. The saved order and the receipt must show the same total.
src/orders/checkout.ts/checkoutCart total = payment = receipt
Multiple discount codes: behavior not documented.
The customer receives the amount paid. The order is marked refunded and its items become available again.
src/orders/refunds.ts/ordersBalance restored · stock returned
Partial refunds: coverage not recorded.
The invitation flow depends on seeded data, and the role check depends on an invitation. Reflow runs them in that order.
Your agent declares prerequisites with needs. Before execution, Reflow explains which work will run, reuse completed results, wait for dependencies, or stay blocked. A little like Terraform for testing.
Understand the execution model ┌──────────────┐
│ seed-data │
└──────┬───────┘
│
┌─────────────┴─────────────┐
│ │
┌──────▼───────┐ ┌──────▼───────┐
│ invite-member│ │ edit-profile │
└──────┬───────┘ └──────────────┘
│
┌──────▼───────┐
│ verify-role │
└──────┬───────┘
▼
┌──────────────┐
│ accept-invite│
└──────────────┘ A refund should restore the balance and return the item to stock. Define commands and comparisons that express those business rules.
Plugins give your agent a testing language for your application, across the browser, database, background jobs and email.
Build application commandsshop.refund_order customer="alex"order.statuspaidrefundedbalance$75.00$100.00stock910shop.expect_balance customer="alex" amount=100shop.expect_stock count=102 assertions passedAn invitation test can pass even when the role selector disappears.
Reflow captures screenshots during test runs and compares them across changes. Your agent checks those differences against the PR’s intended scope and links the relevant captures in its review.
team-invitation/settings/teamsite.snapshotThis PR changes invitation copy. Owners still need to choose a role before sending an invitation.
Show your reviewer the missing control, the changed result and the rule they affect. Your agent can explain which changes belong in scope and which need a closer look.
Keep the screenshots and flow results one click from the review, with a change summary that updates as the run progresses.
Your agent can run independent flows in parallel and read selected knowledge and test results through tool calls.
Start with a run summary, then inspect the relevant knowledge and snapshots. The agent can work across the application without loading the whole repository or every test result into its context window.
manage_execution{ "action": "plan" }Selected target · application test suite
checkoutteam-invitationorder-refundaccount-settingsApply the inspected plan · parallelism 4
Inspect team-invitation with the rule in team-access.md.
The role selector disappeared.
The invitation still sends, but an owner can no longer choose the new member’s role. This PR was intended to update copy.
“An invitation keeps the role the owner selected.”