We plugged Replay QA into a staging URL for our main web app and it genuinely explores like a new tester would, no test script needed. It caught a broken checkout flow on a specific browser/viewport combo that our own manual smoke testing had missed for weeks, and the recording made it trivial to see exactly where it broke. Having it run automatically on every PR and post findings directly in the comments has cut down a lot of the "wait, can someone click through this before we merge" back and forth on our team.
Hey Product Hunt,
Tom here from @replayio.
Most bugs in a live app never get reported. Someone taps a button that doesn't work, tries again, gives up. The only record is a session recording, and nobody has time to watch those (remember those days??).
So how do you fix the bugs nobody tells you about?
That's what Self-healing Mode in Replay QA is for.
It watches your live app's sessions for frustration, using Fullstory's session capture, reproduces the bug in our instrumented browser (every DOM change, network call and JS frame is recorded), and sends a root-cause report to your issue tracker or your coding agent.
When the fix comes back, it reruns the original failure against the PR before you merge.
We ran it on our own production app for two weeks before shipping. 152 PRs opened, 80 merged, every merged one verified against the original bug. Write-up here, including the stuff that didn't work: https://replay.io/blog/what-our-experimental-self-healing-software-loop-shipped-in-two-weeks
It does need real traffic.
If your app doesn't have users yet, start with regular Replay QA. And a person on our team still decided every merge.
Give it a try: https://replay.io/self-healing-mode
We'll be around all day for questions about root-cause analysis, verifying fixes, coding agents, and how session data is handled.
Would love to hear what you think, especially if there's a bug your users have been quietly hitting for months.
What happens if multiple users run into the exact same bug? Does it create multiple reports or just one?
@bengeekly yes. We dedupe and report one instance of the bug, even if multiple user sessions encounter it.
This is really cool! Does this work in CI? Or, can this work for apps that are headless or terminal based?
@arjun_patel1 definitely works in CI! We've got a Replay QA Github bot that runs on PR previews and posts the results in a comment on the PR. To answer your second question, since Replay QA is built upon our time-travel runtime record/replay in our instrumented Chromium fork, headless and/or terminal based apps fall outside the scope.
However, we can test multiple environments: localhost (via ffrp tunnel), dev, staging & prod. But must have an associated web app to capture the runtime recording for analysis. Hope that clarifies things for you.
The rerun-the-original-failure-against-the-PR step is what makes this believable to me — most 'AI fixed it' tools never actually prove the fix reproduces the bug. 80 of 152 PRs merged on your own app is a strong signal too. Is this web-only for now given the session capture, or is there any path for native mobile apps?
@jcbuilds web-only, as you pointed out since it runs in our instrumented Chromium browser. We will focus on recording other runtimes, but no near-term plans for native mobile.
Just want to give a shout out to the team at @fullstory ! What a pleasure collaborating with them to incorporate their incredible user session capture to enable a relatively frictionless setup. With a single prompt for your coding agent, Replay QA's Self-healing Mode can be up-and-running in minutes.
The 'needs real traffic' note is helpful, good to know when to start with regular Replay QA vs. self-healing. Does the session capture work across authenticated flows or mainly public pages?
@milena_paz1 it can test authenticated flows. You can provide one or more test account credentials and also let our agents create their own accounts.