Skip to main content
Percher is still being built and account creation is paused — get notified when it opens.

Crash diagnostics

Crash reports and runtime troubleshooting; external AI analysis is currently disabled

Ask your agent
My app stopped working. Find out why and fix it.Read the guide at percher.app/docs/crash-diagnostics
How it works, with exact details

Crash detection and basic reports continue to work. External AI analysis is currently disabled across Percher. An app's opt-in setting alone does not send logs to an external AI provider. App settings show the current availability.

Anthropic Claude is an optional future provider. External analysis would require Percher to complete the provider-account and transfer safeguards, reactivate the service, and have the app owner's opt-in. OpenRouter remains withdrawn and is not a fallback. Redaction reduces exposure but cannot guarantee that every personal detail is removed from logs.

The watchdog checks for exited Docker containers every five seconds by default. A non-zero exit detected on the next poll queues a report, and OOM kills (exit code 137) get a deterministic memory-limit explanation without external AI. Reports are available in the app dashboard. No new external AI explanation is generated while the service is disabled.

For AI assistants with MCP: use percher_doctor with mode="runtime" to retrieve runtime troubleshooting information and the latest applicable crash report. Basic reports remain available without external AI analysis. Stale reports (>24h old) on apps that have recovered are filtered out.