Detect
Capture closure context immediately
Identity, termination metadata, and timing are captured as the event occurs.
Diagnose
Map evidence to dominant cause
Deterministic classification returns a bounded confidence signal and caveats.
Act
Execute the next move with proof
Copy-ready recommendations and exportable evidence improve escalation quality.
Features
Coverage Across Real Termination Paths
WhyDidItClose classifies practical closure paths including:
- normal quit
- force quit
- external kill / SIGKILL pathways
- crash-related exits
- policy and runtime pressure terminations when evidence exists
Decision-Ready Output
Each analyzed event includes:
- dominant cause
- confidence level and rationale
- end state
- concise explanation
- recommended next action
Confidence Interpretation
| Confidence | Signal quality | Operator behavior |
|---|---|---|
| High | Strong direct OS evidence | Execute the recommendation and attach export if escalating |
| Medium | Mixed direct + correlated evidence | Validate one adjacent signal before escalation |
| Low | Limited evidence | Treat as hypothesis and gather additional logs |
Timeline Context for Faster Triage
Per event, WhyDidItClose captures context needed for reliable handoff:
- app identity and process context
- launch and termination timing
- reason metadata and attribution hints
Local-First by Design
- No account required for core diagnosis.
- No mandatory cloud dependency.
- Export only when you explicitly choose to share evidence.
Workflow Acceleration
- Pro Lifetime: export-heavy individual triage workflows.
- Team Plan: shared support and QA operational rollout.
Trust and Release Readiness
- Signed and notarized direct distribution build.
- Published checksum verification on the download page.
- Legal and support workflows aligned to production-grade rollout.