replay re-runs a recorded action sequence through the real action pipeline (with per-step effect checks), and fork clones the live browser into up to 8 parallel targets so a cohort can fan out from the same state.
CLI and cURL examples use $RT and browser b1 (Sessions).
Replay a sequence
replay takes steps — [{action: {verb, target, …}, expect_*}] entries,
where action is the same body actions/{verb} accepts — and runs each
through the real action pipeline. After every step’s settle it can check
expect_url_contains, expect_selector (a CSS that must resolve), or
expect_eval (JS that must eval truthy). stop_on_fail halts at the first
mismatch, step_timeout_ms caps each step, and target_id replays into a
specific tab; the reply carries {ok, steps_run, results}.
Fork the session
fork clones the browser’s current state into count new tabs (1–8) and
returns their target ids — a worker cohort that starts from identical cookies,
DOM, and scroll position. Pass url to point every fork somewhere new; omit
it to keep each clone on the page it forked from.