Have your agent run the application it is changing.

Open pages, follow user journeys, assert behavior, and keep screenshots at the points that matter.

How it works

The Browser plugin executes declared commands against your selected target. Your agent writes a deterministic flow with assertions and named captures, runs it with plan and apply, and can hold a failed run open to inspect the page where it stopped.

The reviewer can see whether the invitation worked and inspect the screen where it failed.

An application target

Use path-only URLs in flow source so the same journey can run against a selected local app or reachable preview.

Assertions and captures

Assert the required behavior and capture named screens so reviewers can inspect the result.

Repair by your agent

Reflow runs no model inside the runner. Your coding agent holds the failed run, inspects it and edits the flow. Applying the edited flow again continues on the held browser and plugins from the failed step. The failed original stays alongside the new result.

A copy change removed the role selector.

This example compares the invitation screens and shows the agent’s finding about the missing control.

reflow / Team invitationsIllustrative example
Change Summary

Update invitation copy

1 changed screen
invite-memberPassed
team-invitation/settings/team
Beforemain
AcmeWorkspace Invite a teammate Add someone to your workspace. Email address sam@acme.test RoleEditor Send invitation
Afterthis change
AcmeWorkspace Invite a teammate Add someone to your workspace. Email address sam@acme.test Role selector removed Send invitation

Snapshot delta · team-invitation Before: role selector present. After: role selector removed.

The test passed. The screen changed.site.snapshot
Agent reviewOutside scope

The role selector disappeared.

This PR changes invitation copy. Owners still need to choose a role before sending an invitation.

team-invitationteam-access.md

Executable Browser steps

Use the setup guide to select plugin versions and configure private connections for your application.

Read the execution language
---
providers:
  site: Browser
---

site.open url="/settings/team"
site.click selector="[data-testid=invite-member]"
site.expect selector="h2" text="Invite a teammate"
site.snapshot name="team-invitation" selector="[data-testid=invitation-form]"

Browser deltas

Give your agent snapshot comparisons to judge which application changes belong in the scope of your PR.