Playground: record and debug

The playground places a live cloud browser beside the flow editor. Interact with the real page and the recorder appends each captured action as a deterministic RFL line. A navigation closes the current step so the document keeps the same step boundaries you exercised in the browser.

A short recording can produce a step like this:

open /products
click role=button name="Add to cart"
expect testid=cart-badge text="1"

Selector validation

Before a recorded line reaches the document, Reflow checks that its selector resolves to exactly one actionable element on the live page. It tries the captured selector and other low-cost candidates first. When several valid candidates remain, a small model can choose among only those candidates.

The final line is checked again before it is accepted. If the page changed, no selector is unique, or validation times out, the capture is surfaced as recorded action not added instead of being kept silently.

Replay and debug

Use play to run from the current point, step over to execute one RFL unit, or play until cursor to stop before the selected line. The editor highlights the current execution row while the browser pane shows the live viewport. A gutter click provides the same run-to-line control.

Recording and replay share one flow document. If you edit while new captures arrive, the playground keeps the recorded lines pending until you apply them, so local edits are not overwritten.

The agent uses the same browser

The live session is also the agent surface. MCP tools such as open_session, act, snapshot, and screenshot drive and inspect the same kind of live browser. See the MCP reference for the connection command and the complete session loop.