Crashes

Frontend errors are captured on their own. The Interface SDK reports every uncaught exception and unhandled rejection from real browser sessions, with no code to add. They arrive here grouped by fingerprint, the way Sentry groups them, so a thousand instances of one bug read as one row instead of a thousand. list shows those groups with their occurrence counts and how many users each one hit; stats plots total crash volume over time to catch a regression the moment a release ships it.

From a group, occurrences walks its individual events and get opens one in full, with the stack trace and the breadcrumb trail that led up to it. Each group row also carries an example event id, so a quick drill-in never requires paging. It is the browser-side counterpart to the request log: what broke on the client, callable the same way, from a terminal command or a few lines of code.