Private beta · waitlist openerror monitoring for react & next.js

Catch every crash Fix it with your own agent.

One wrapper captures every crash in your React or Next.js app with a session replay, console logs, network requests, breadcrumbs and a screenshot. BugBash explains it in plain English and writes a fix prompt for the coding agent you already use.

You're on the list.We'll email [email protected] when BugBash opens.

In private beta. Join the waitlist for an invite.

React / Next.jsClaude Code / Cursor / Codex
crash timeline/checkoutsample
00:03FetchGET /api/session
00:05Clickbutton "Pay now"
00:05GET failed/api/session returned 401
00:06Crash capturedTypeError: Cannot read properties of undefined (reading 'email')
BugBash/sample project01 Replay
Recorded in the BugBash dashboard. The project, the shop and every crash in it are sample data.
‹01› capture

One wrapper records the whole crash.

Wrap your app once in <BugBash>. When something breaks, the crash lands in your inbox with everything that happened just before it.

app/providers.tsxNext.js
'use client'

import { BugBash } from '@bugbash/sdk'

export function Providers({ children }) {
  return (
    <BugBash      projectKey="demo-project"      environment="production"      sessionReplay      maskAllInputs    >      {children}
    </BugBash>  )
}
Attached to every crashsample: /checkout · TypeError
01

Session replay

What the user saw and clicked before it broke. Inputs are masked by default.

00:12 · 1280×900 · 90 events
02

Console logs

Log, warning and error lines in the order they fired.

[error] TypeError: Cannot read properties of undefined (reading 'email')
03

Network requests

Recent requests with status codes and timing, so the failed call stands out.

GET /api/session → 401 in 120ms
04

Breadcrumbs

Clicks, form submissions and navigation, right up to the crash.

+4.5s click button "Checkout"
+6.0s navigate to /checkout
+9.0s click button "Pay now"
05

Screenshot

The screen at the moment it went wrong.

+10.5s crash captured on /checkout
‹02› replay

Watch the session that crashed.

The replay shows what the user saw, with the network log, console and stack lined up underneath. Click any row to jump the replay to that moment.

Session replay of a sample checkout that failed with HTTP 503: the recorded storefront with the 'Checkout submit failed: HTTP 503' signal, a replay timeline, the scrubber with event markers, and the network log listing POST /api/checkout 503.
  1. 1

    Masked by default

    Inputs are masked in the recording. The shopper's email shows up as [REDACTED].

  2. 2

    Every event on the scrubber

    Clicks, requests and the crash sit on the timeline. Skip the gaps or slow it down.

  3. 3

    The failed request

    POST /api/checkout returned 503. Click the row and the replay jumps there.

‹03› explain

Every crash comes explained.

Each issue gets an AI analysis in plain English: what broke, the likely cause, a next step and how confident it is. Every finding points at the evidence it relied on.

  1. 1

    The crash timeline

    Clicks, navigation and requests, ending at the captured TypeError.

  2. 2

    Cited evidence

    The error, the stack, the 401 from /api/session and the user's actions, each tagged.

  3. 3

    A next step, and an honest confidence

    Open CheckoutForm.submit and check where the object holding 'email' is set.

Confidence Medium
“The stack points to the exact line, but the capture does not show why the object is undefined.”
BugBash issue page for the sample issue 'Checkout crashes when user clicks Pay now' (critical, /checkout, 37 events, 33 sessions): a crash timeline ending in a failed GET /api/session that returned 401 and a captured TypeError, the stack, and an AI analysis panel with cited evidence, the likely cause, a next step and medium confidence.
The Fix prompt tab for the sample issue: a markdown prompt with the route, the error, each step the user took with timings, the failed GET /api/session request that returned 401, the console error and the top stack frames, with Bundle and Copy prompt buttons.
‹04› fix prompt

Hand the fix to your own agent.

The fix prompt collects the route, the error, each step the user took, the failed requests, the console and the stack into one markdown prompt, built from the captured evidence.

paste into →Claude CodeCursorCodex
  • The agent starts from what actually happened: the steps, the 401, the error line.
  • You make and review the change in your own editor, with the tools you already trust.

BugBash never touches your repo. No commits, no pull requests, no access to your code.

‹05› test

Turn the crash into a green check.

Once the fix is in, BugBash can turn the crash into a Playwright regression test that starts from the steps the user took. Review the spec, then run it against development, staging, preview and production.

  • Standard Playwright: readable, editable, yours to keep.
  • Every run keeps its history and artifacts per environment.
checkout-pay-now.spec.tssample
// From issue 38f110af: Checkout crashes when user clicks Pay now
import { test, expect } from '@playwright/test'

test('checkout: Pay now does not crash', async ({ page }) => {
  const errors = []
  page.on('pageerror', (e) => errors.push(e))

  await page.goto('/')
  await page.getByRole('link', { name: 'Cart' }).click()
  await page.getByRole('button', { name: 'Checkout' }).click()
  await page.getByRole('button', { name: 'Pay now' }).click()

  expect(errors).toEqual([])
})
developmentpassed
stagingpassed
previewpassed
productionpassed
‹every morning›

See what changed since yesterday.

Crashes are grouped into issues and ranked by what needs review, so the first thing you open is the one worth your time.

Overview
The BugBash overview for a sample project: 4 new, 1 regressed and 1 spiking issue in the last 24 hours, a Needs review list whose top issue shows the AI next step with Open issue and Copy fix prompt buttons, and a 7-day stability card.
Issues
The Issues inbox for a sample project: grouped issues sorted by needs review, each row with severity, route, replay availability, priority and confidence, a 14-day sparkline, sessions, events, status and last seen, with New, Regressed, Spiking and Likely noise filters.
overview

What changed in the last 24 hours

New, regressed and spiking issues, the ones waiting for review with their next step, and crash-free sessions over the week.

issues

Ranked by what needs review

Severity, confidence and whether a replay exists on every row, with filters for new, regressed, spiking and likely noise.

alerts

Alerts where you already are

Email, Slack or Discord, so you hear about a crash without watching a dashboard.

‹private beta›

Now in private beta.

Join the waitlist and we'll send you an invite as spots open.

You're on the list.We'll email [email protected] when BugBash opens.

Questions? [email protected]

React and Next.jsWorks with the agent you already useNever touches your repo