loupfeed › Crash & error tracking
For every user who writes to you, plenty just close the tab. loupfeed catches unhandled errors on their own, groups them by signature, resolves the stack back to your source, and attaches the session that led there — so the silent failures show up next to the reported ones, in the same inbox.
Web and React Native · V8, Hermes and JavaScriptCore stacks parsed · replay attached per occurrence.
Errors are normalized into structured exceptions the moment they are caught. loupfeed parses both major stack dialects, marks which frames are yours, and anchors everything on the first one that is — so an issue is titled by your code, not by whatever library happened to be on the stack.
at fn (file:line:col)) and JavaScriptCore or Safari (fn@file:line:col)node_modules and native or internal frames are marked out of appSymbolication is a server-side join against the manifest and source maps for that release, so a minified production stack still lands on a real line in your repo.
A crash group is every event sharing a fingerprint — the error type plus the top in-app frame. Grouping is derived from the flat event list rather than stored as its own record, so it behaves identically whether you are on in-memory, SQLite or DynamoDB.
open, resolved, wontfixAn automatic crash carries the same envelope a human report does. That is the point of putting them in one platform — you are not switching tools to find out what happened.
The rolling buffer is frozen and uploaded on the crash, so you watch the thing happen instead of reconstructing it.
Navigations, clicks and whatever you recorded yourself, in order, ending on the error.
The identified user and your own context keys — plan, account, tenant, whatever you set.
There is nothing extra to wire up. Unhandled errors and promise rejections are captured once you call init, and every scope value you already set for feedback rides along on the crash.
Crashes are exposed over MCP the same way feedback is. Your agent lists the open groups, pulls one with its resolved frames, breadcrumbs and replay, fixes the code, and marks it resolved — without you copying a stack trace into a chat window.
Free to self-host, forever. Same SDK you already installed for feedback — crashes just start arriving.