happier-diagnose

Root cause analysis for broken Happier sessions uses evidence-based log and doctor analysis to pinpoint failures. The diagnosis requires a valid session ID to pull the correct transcripts and identify the exact failure point.

Auth troubleshooting and provider rate limit diagnosis are performed by running built-in doctor and auth status checks. This workflow analyzes session metadata and provider session IDs to identify connectivity or authentication failures.

Diagnosing a misbehaving Happier daemon involves applying evidence-based log analysis to identify supported root causes. The process uses specific daemon log lines and doctor fields to output high-confidence failure triage.

Private diagnostics uploads and sanitized GitHub issue creation are supported through optional consent-based sharing. This allows users to securely share diagnostic bundles with maintainers or submit public bug reports without exposing sensitive data.

A Happier session ID is required to begin triage, as it retrieves session metadata and sessionLogPath. This mandatory evidence anchoring ensures the root-cause diagnosis references the correct transcripts and provider logs.

Evidence anchoring is required for Happier session troubleshooting to ensure root-cause output maintains high confidence. Diagnoses are only determined when supported by specific log lines, doctor fields, or repo source references.