Superpowers
for your agent

Replay records your app so your agent can understand everything that happened, down to the finest detail.

From bug to fix —
without touching DevTools

See how Replay MCP lets your agent dive in and explain the problem.

Button doesn't work

Creating a new task does nothing

Chat transcript with Replay MCP

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):

  1. Line 83 shows the function was called once (hit count: 1)
  2. Lines 84-90 build the payload object
  3. Line 92 closes the modal with setCreateModalOpen(false) (hit count: 1)
  4. 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:

  1. Builds the payload object ✓
  2. Closes the modal ✓
  3. 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.

Battle tested.

Replay helps some of the largest companies record their E2E tests at scale and verify the correctness of mission critical software.

Case Studies

Hear from Replay teams directly

Testimonials

See what time travelers are saying

“Next.js App Router is now stable in 13.4. Wouldn’t have been possible without Replay, we investigated so many (over 20) super complicated bugs that using traditional debugging would have cost us days to investigate.”

Tim Neutkins

@Co-author of Next.js

“I think Replay has a very good chance of creating a new category around collaborative debugging”

Guillermo Rauch

@Founder of Vercel

“When I see a hard-to-reproduce issue in GitHub, I ask for a replay.”

JJ Kasper

@Co-author of Next.js

“If I don't immediately know the answer to a bug, I immediately reach for Replay.io. It's like HMR for repros.”

Sebastian Markbåge

@React Maintainer

“Replay.io is galaxy brain tooling. Real gamechanger.”

Dan Abramov

@React Maintainer