Let your agent check the data behind the screen.

Save query results as snapshots and compare them across runs. Your agent can inspect a changed balance or order status alongside the browser journey.

reflow / PostgreSQL · refund checkIllustrative example
verify-refund.mddb: PostgreSQL
db.query sql="SELECT id, status, refunded
FROM orders ORDER BY id"
key="id" checkpoint="orders"
orders / rows.jsonEarlier runCurrent run
id keystatusrefunded
1041paid0.00
1042refunded25.0020.00
1043paid0.00
3 rows retained · amounts in USD
Retained before → after1042
refunded25.0020.00
Agent review · examplerefunds.md

Full refunds return the entire $25.00 payment.

The order says refunded. $5.00 is missing. The captured rows show $20.00 returned. Check the refund amount before merging.

Capture the rows that answer your question.

Query the test database for the order, entitlement or account state your flow needs to inspect. PostgreSQL queries run in a read-only transaction and retain the returned columns and rows.

  • Column names and row values
  • Stable ordering with a unique key
  • Original query snapshots

Keep the results stable enough to compare.

Use a unique key or an explicit sort order. Reflow compares the retained results; your agent reads the before and after values to explain which business facts changed.

An order is marked refunded, but the refunded amount is lower than the amount paid. Your agent can identify the mismatch, check the refund rule and bring both query results into review.

Bring the evidence into PR review

A query result retained as a checkpoint

Keep the database connection string in the private PostgreSQL connection. The key must be unique and non-null in the returned rows. Test setup writes use a separate execute command with writes explicitly enabled.

Your agent can inspect the installed plugin’s commands and write the flow using your application knowledge. Select the plugin version in the flow’s requirements.

Flow excerptPostgreSQL
---
providers:
  db: PostgreSQL
---

db.query sql="SELECT id, status, refunded FROM orders ORDER BY id" key="id" checkpoint="orders"

Plugin requirements and private connection settings are configured separately.

Check the rest
of the application.