Screen recorder that writes bug reports

The idea

The most expensive sentence in software is it doesn’t work, sent by a support rep with a cropped screenshot. The developer spends forty minutes asking which browser, what account, what did the console say. Screen recording itself is settled commodity territory — the crowd gave clear replaceable verdicts on polished recorders around $13/mo — so a recorder alone is not a product anymore.

The wedge is the artifact a recording becomes. A non-technical teammate records once; the extension captures the DOM replay, console errors, and failed requests underneath the clicks, and AI writes the numbered repro steps with the right technical context attached to each step. The reporter never learns what a console is, and the developer gets a report better than most engineers write by hand. Jam proved the capture side; the AI-written, auto-filed report is the differentiator, priced under Jam’s team tiers at $10/seat.

Who pays

The buyer is an engineering lead or support manager at a 10-200 person software company, paying $10/seat/mo for support and QA seats. The pitch is arithmetic: one avoided repro session pays for the team’s month. Distribution is bottom-up — the free tier spreads when a developer receives one good report and asks what produced it — plus Chrome Web Store search and comparisons against Jam and BirdEatsBug.

MVP scope

• MV3 extension recording rrweb replay plus console, network, and click events
• Client-side redaction of input values and auth headers
• Claude-written report: numbered steps, expected vs actual, technical context per step
• Shareable replay page with error-highlighted timeline
• One-click filing to Linear and GitHub Issues
• Skip for v1: Firefox/Safari, desktop app capture, Jira integration, team analytics

Build ReproBot, a Chrome extension that lets support and QA staff record a bug once and get a developer-ready report written for them. Stack: Chrome extension (Manifest V3) using rrweb for DOM session capture, a Next.js web app for report viewing, Claude API for report writing, Supabase for auth, Postgres, and storage.

Core flow: user clicks the extension icon and hits Record. The content script captures an rrweb DOM replay plus a synchronized event log: clicks with element selectors, inputs (values masked by default), console errors and warnings, and failed or slow network requests with status codes. User reproduces the bug, clicks Stop, adds one line about what they expected. Everything uploads to Supabase; the server sends the event log (not the video) to Claude, which writes numbered reproduction steps, expected vs actual behavior, and a technical context section pairing each step with the console errors and network failures that fired during it.

The shareable report page shows the rrweb replay alongside the AI-written report, with a timeline that highlights which step each error belongs to. One-click filing to Linear and GitHub Issues with the report as the body and the replay link attached.

Non-obvious details: redact input values and Authorization headers before anything leaves the browser; capture a rolling 30-second pre-record buffer so users who click Record after the bug still catch it.

Pricing: free for 5 reports/mo, $10/seat/mo unlimited with Linear/GitHub filing. Stripe billing.