browser-replay
Replay a recorded session trajectory against the same URL or a mutated variant; uses browser-selectors embedding similarity to recover from DOM drift
Best for Regression testingWorks with GitHub
⌘source
- author
@ruvnet- repo
- ruvnet/ruflo
- language
- TypeScript
★46kstars
5.1kforks
May 5, 2026
✦overview.md
Key Features
- ·Replay recorded browser sessions
- ·Support for session ID and positional args
- ·Optional URL mutation for variant testing
- ·Tolerance parameter for DOM drift recovery
- ·Uses embedding similarity for selector matching
Use Cases
- →Regression-test a UI flow after a deployment
- →Reproduce a bug captured in a prior session
- →Compare two runs of the same flow for visual diffing
Best for
- ✓Regression testing
- ✓Bug reproduction
- ✓UI flow verification
Not ideal for
- !Exploratory testing
- !Interactive debugging
FAQs
name
browser-replay
description
Replay a recorded session trajectory against the same URL or a mutated variant; uses browser-selectors embedding similarity to recover from DOM drift
argument-hint:<session-id> [--url <new-url>] [--mutate <json>] [--tolerance <0..1>]
allowed-tools:mcp__claude-flow__browser_open mcp__claude-flow__browser_close mcp__claude-flow__browser_click mcp__claude-flow__browser_fill mcp__claude-flow__browser_type mcp__claude-flow__browser_press mcp__claude-flow__browser_select mcp__claude-flow__browser_check mcp__claude-flow__browser_uncheck mcp__claude-flow__browser_hover mcp__claude-flow__browser_wait mcp__claude-flow__browser_screenshot mcp__claude-flow__browser_snapshot mcp__claude-flow__browser_eval Bash Read
Browser Replay
Re-drive a recorded session trajectory. Used for regression testing, deterministic re-runs, and as the verification path that browser-record plus browser-selectors actually produces something replayable.
This skill is the load-bearing assumption of the v0.2.0 architecture. ADR-0001 Verification §4 requires ≥80% replay success across 10 distinct sites of varying drift profiles before the proposal moves from
Proposed→Accepted. If you find replay unreliable, capture the failure modes infindings.mdand report them up the ADR.
When to use
- Regression-testing a UI flow after a deploy.
- Reproducing a bug captured in a prior session.
- Comparing two runs of the same flow for
browser-screenshot-diff. - Forking a session (
/ruflo-browser fork) and replaying the parent before mutating.
Steps
- Locate the source session:
npx -y ruvector@0.2.25 rvf status <session-id>.rvf - Load the trajectory:
Each line isRead .../trajectory.ndjson{ts, action, args, selector, result}. - Open a fresh browser via
mcp__claude-flow__browser_open(target URL = original or--urloverride).
$install
1-click copynpx skills add ruvnet/ruflo --skill browser-replaySafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.