An application target
Use path-only URLs in flow source so the same journey can run against a selected local app or reachable preview.
Open pages, follow user journeys, assert behavior, and keep screenshots at the points that matter.
open /settings/team
│
▼
click "Invite member"
│
▼
fill email / choose role
│
┌────┴────┐
▼ ▼
assert snapshot
└────┬────┘
▼
retained resultThe 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.
Use path-only URLs in flow source so the same journey can run against a selected local app or reachable preview.
Assert the required behavior and capture named screens so reviewers can inspect the result.
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.
This example compares the invitation screens and shows the agent’s finding about the missing control.
team-invitation/settings/teamSnapshot delta · team-invitation Before: role selector present. After: role selector removed.
site.snapshotThis PR changes invitation copy. Owners still need to choose a role before sending an invitation.
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]"