An application target
Use path-only URLs in flow source so the same journey can run against a selected local app or reachable preview.
Have your agent run the application it is changing.
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 resultHow it works
The Browser plugin executes declared commands against your selected target. Your agent can inspect live sessions while authoring, then save a deterministic flow with assertions and named captures for repeatable execution.
The reviewer can see whether the invitation worked and inspect the screen where it failed.
Assertions and captures
Assert the required behavior and capture named screens so reviewers can inspect the result.
A bounded repair loop
Inspect the original failure, propose a repair, and execute again. Keep the failed original alongside the candidate 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
1 changed screenUpdate invitation copy
invite-memberPassed
team-invitation/settings/teamThe test passed. The screen changed.
site.snapshotAgent 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]"