Crash diagnostics
AI-analyzed crash reports, surfaced via percher_doctor mode=runtime
Opt-in per app. AI-powered crash analysis is disabled by default — turn it on in app settings (Crash diagnostics → Enable) to start receiving banners. The crash watchdog itself always runs; only the AI explanation step is gated by the opt-in.
Once enabled: when your app crashes, Percher collects logs, redacts secrets, and runs AI analysis (Anthropic Claude primary, OpenRouter fallback) to explain what went wrong. Crash reports appear as a banner on your app's dashboard page with a copy-paste fix prompt you can hand to your AI assistant.
The watchdog monitors Docker container events in real time. If your app exits with a non-zero code, it queues a crash analysis within seconds (when the flag is on). OOM kills (exit code 137) are flagged automatically with memory limit suggestions.
For AI assistants with MCP: use percher_doctor with mode="runtime"to fetch the latest crash report directly in chat — the response's recovery.promptincludes the AI-generated explanation, suggested fix, and log tail (the same payload the older diagnose tool returned). Doctor is the single recovery hub on the MCP surface. Stale reports (>24h old) on apps that have recovered are filtered out so the assistant doesn't surface irrelevant advice.