// for bug fixing & incident response
Sentry error → root cause → PR. While you sleep.
Production bugs don't wait for business hours. Leroy watches Sentry, picks the bugs worth fixing, traces the root cause, writes the fix and a test, opens the PR, and reviews its own diff. You wake up to green checks — not red alerts.
// triggered by
SUB-87 · TypeError on /billing
Sentry alert: 47 events in 6 minutes
02:14 · Cannot read 'amount' of undefined
Root cause: webhook fires before charge resolves
02:17 · traced through 3 files + the stack
Fix + regression test, PR #312 opened
02:20 · self-reviewed · awaiting your merge
Slack: posted to #incidents with the diff
02:21 · "fixed, here's why it happened"
// the flow
Four steps. Zero of them yours.
// 01 detect
Reads Sentry
Watches for new issues, dedupes, and decides what's worth fixing now vs. noise.
→
// 02 diagnose
Traces root cause
Follows the stack into your code, reproduces the path, finds the actual cause — not just the symptom.
→
// 03 fix & ship
Writes the PR
Fix plus a regression test, self-reviewed, with a plain-English write-up of what broke and why.
// in scope
The bugs Leroy takes off your plate
The crash-class errors that fill your Sentry inbox — the ones that are annoying to triage but rarely need a human's judgment to fix.
✓
Null / undefined crashesThe "cannot read X of undefined" that's 30% of every Sentry feed.
✓
Unhandled promise rejectionsMissing awaits, swallowed errors, race conditions on load.
✓
RegressionsSomething that worked last week and doesn't now — bisected and fixed.
✓
Edge-case input errorsThe empty array, the weird timezone, the emoji in the name field.
✓
500s & timeoutsBackend errors with a clear stack — found, fixed, tested.
✓
Browser-specific breakageThe bug that only happens on Safari < 16.3, reproduced and patched.
Stop starting your day with a list of fires.
// other angles
Not quite you?
// closed beta
Wake up to green checks.
Leroy is in closed beta — we're onboarding the first 50 users by hand. Connect Sentry and tell us what your worst recurring bug looks like.