Error captured in production
Your app throws an unhandled exception. Patchly's SDK intercepts it — browser or server — and sends the stack trace, breadcrumbs, and release context to the ingest API within milliseconds. No page reload, no user impact.
Exception caught
TypeError: Cannot read properties of undefined (reading 'id')
Capture
Repeated failures grouped into one issue
The same failure hits again from three different users. Patchly deduplicates by fingerprint — stack + message + release — and increments the event counter. When the threshold is crossed, it opens exactly one GitHub issue, not five.
GitHub issue opened automatically
Patchly's bot opens the issue in your repository with the full stack trace, affected-user count, release SHA, and a formatted breadcrumb trail. Your team can triage it like any other issue — label, assign, close.
Source-aware repair note posted as a comment
Patchly's AI reads the stack trace, fetches the relevant source files from your repository (resolved via source maps), and posts a repair note as a GitHub issue comment. The note includes a concrete diff — not a generic suggestion.
Fix applied, issue closed
Your AI coding agent — Claude Code, Cursor, or similar — fetches the repair note via the Patchly MCP server, applies the diff, and marks the patch as proposed. The GitHub issue closes. The loop is complete.
Done
Patch proposed · Issue closed · Loop complete
Resolved