How does Replay record my tests?

Replay works by swapping in a Replay-instrumented browser in your CI config. When a test runs, Replay captures every DOM mutation, network request, and JS execution deterministically — so the recording is a perfect, replayable trace of exactly what happened.

What kind of analysis does the agent provide?

For each failing test, Replay posts a PR comment with a root cause statement, a confidence score, the exact line of code that caused the failure, and an evidence trail showing the sequence of events leading up to it. If the failure has a clear fix, it includes a suggested code change.

Does Replay only work with React?

No — Replay works with any JavaScript or TypeScript application. React apps get deeper analysis because Replay can inspect component state and re-renders, but Replay captures full execution data for any JS stack.

How long does analysis take?

Usually a few minutes after the test run completes. Replay posts its analysis as a PR comment, so your developer sees the root cause and suggested fix before they even open the CI logs.

What if the agent's analysis is wrong?

Replay includes a confidence score with every analysis, so you can tell at a glance how certain it is. Every analysis also links to the full recording so you can open it in Replay DevTools and inspect every frame yourself.

Does recording slow down my CI?

Minimal overhead — comparable to screen recording. Most teams run Replay in CI without noticing a difference in build times.

How much does this cost?

Replay Growth is $299/month (billed annually) or $349/month (billed monthly), and includes 500 AI analyses per month. Start on the Free plan (25 analyses/month) with no time limit. See full pricing →

Replay — E2E test failures analyzed automatically

Your CI fails.
Your team debugs. Repeat.

A test fails in CI. The test assertion tells you what failed—not what broke. Someone opens DevTools, reproduces it locally if they're lucky, and eventually figures out the root cause. That's an hour per failure. Multiply by your team.

Your coding agents make this worse. They can write code faster than ever, but when something breaks at runtime they're debugging blind — guessing at fixes, looping on the same failure, burning tokens without making progress. The bottleneck isn't writing code. It's what happens when it breaks.

So teams do the rational thing: they avoid writing more automated tests, because the maintenance overhead isn't worth it. Coverage stagnates. Confidence erodes.

Give your agent the power of time-travel

Replay captures a deterministic recording — every DOM change, network request, JS execution frame, and state update. Using Replay MCP, your coding agent can analyze the recording, trace the exact causal chain from failure to root cause, and deliver the root cause and a suggested fix. No guessing. No manual debugging. No human required.

The form to add a new task isn't doing anything

I'll investigate why the form to add a new task isn't working. Let me start by exploring the recording to understand what's happening.

Let me look at the CreateTaskModal component more closely to understand its implementation, especially the form submission logic.

I can see the form submission logic. Line 53-54 shows handleSubmit was called once, but let me check where the onSave callback leads to. Let me look at TasksListPage to see how the modal's onSave is handled.

I found the issue! Looking at handleCreateTask (lines 73-93):

Line 83 shows the function was called once (hit count: 1)
Lines 84-90 build the payload object
Line 92 closes the modal with setCreateModalOpen(false) (hit count: 1)
But there's no fetch call to actually save the task!

The function closes the modal at the end, but it never makes a network request to persist the new task. The payload is built but never sent to the server.

Root Cause

The handleCreateTask function in TasksListPage.tsx is missing the API call to create the task. It:

Builds the payload object ✓
Closes the modal ✓
Does NOT call fetch to POST the task to the backend ✗

Compare this to line 65-70 where fetch is used to load deals - a similar pattern should exist after building the payload on line 92, but it's missing. The function just closes the modal without actually saving anything.