How it works

From URL to bug report.
Automatically.

Give Replay QA a URL. It explores your app, records every session with our time-travel debugger, and delivers a root cause and suggested fix for every bug it finds.

What you get

Root cause. Suggested fix. Full recording.

Every bug Replay QA finds comes with everything your agent needs to fix it — not just “something broke.”

Bug found
confidence: high

Checkout button does nothing on mobile Safari

Root cause

handleSubmit is never called because the button is rendered outside the <form> element after the responsive layout change on screens under 768px.

Suggested fix

Move the button inside the form, or add form="checkout-form" to the button element.

Evidence

Replay recordingDOM mutationsNetwork traceReact state

Example output — actual reports are generated from your app's real runtime data.

Testing continuously

Connect your GitHub repo

The URL drop is an on-demand check. When you want a quality gate that stays on as your team ships, connect a repo instead — same autonomous QA, running on every change. No test suite, no pipeline config.

01

Add your repo URL

Paste a link to your GitHub repository — the same “paste a link to your thing” pattern as the URL drop.

02

Authenticate with GitHub

Sign in with your GitHub account. One technical lead can complete setup — no procurement, no engineering ticket.

03

The Replay QA app installs

The GitHub app installs on your repo. No existing Playwright suite, no playwright.config.ts changes, no separate bot to wire up.

04

Choose your run cadence

Run on every main-branch update, on every pull request, or both. On PRs, root cause and a suggested fix are posted right on the pull request.

Connect your GitHub repo

Ask Your Agent

One prompt. Your agent does the rest.

Try feeding this prompt to your coding agent to see the magic unfold.

Set up a continuous QA loop for the app we're building using Replay QA (https://qa.replay.io). …

Works with Codex, Claude Code, Cursor, and any agent you're using.

The technology

Underneath it all: our time-travel debugger.

Whether you're running Replay QA on a web app or analyzing a CI failure, the same recording engine is at work. Replay captures the full browser runtime deterministically — making AI analysis possible where it wasn't before.

Render chainsWhich component re-rendered, what triggered it, what changed
State flowRedux actions, React state updates, context changes across the component tree
Network timingEvery request and response, with exact payload and timing data
JS executionEvery function call on every frame, with arguments and return values
DOM mutationsWhat changed in the DOM, when, and what code caused it

This isn't guessing from error messages. It's reading the actual execution.

Test your app for free.

Give Replay QA a URL. No test suite, no QA team, no credit card required.

No test suite · No credit card · Just a URL

Using GitHub?Connect a GitHub repo for continuous testing