Test interface behavior in a real browser and save actions, checks, and screenshots in a replayable RVF session file. Use recorded sessions to repeat tests, investigate CI failures, and compare screenshots against an earlier baseline.
UI test recipe -- composes browser-record (capture) + browser-replay (verify) so every test produces a replayable RVF artifact, not an ephemeral run
Review the instructions the agent will receive before you install.
Automated UI testing. Now backed by a recorded RVF session container instead of an ephemeral run, so every test produces a replayable artifact.
browser-record:
--kind browser-session.browser_open, browser_click, browser_fill, browser_type, browser_select. Each action emits a trajectory-step.browser_wait before assertions.browser_get-text / browser_get-value / browser_get-title / browser_get-url. Validation outcomes go into findings.md inside the RVF container.<step-id>.png.trajectory-end --verdict pass|fail, rvf compact, AgentDB index in browser-sessions.--against <prior-session-id>: invoke browser-screenshot-diff to compare the new run with a baseline.browser_back / browser_forward for history navigationbrowser_reload to refresh the pagebrowser_scroll to scroll to elements or coordinatesbrowser_close alone — it ends with the session-end protocol.browser-selectors (host:intent), so the next test can find them by embedding similarity.aidefence_is_safe before any LLM-facing summary; injection-flagged content is quarantined to findings.md./ruflo-browser replay can re-drive.browser_wait before assertions to handle async rendering.--against <id> on the next run.browser_eval for custom JavaScript assertions — but redact any returned strings via the aidefence_is_safe gate before logging.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.