What it solves
Crash reports
Best for users who want faster support while understanding privacy boundaries.
Renderer error capture
The app has plumbing to report renderer-side errors with useful context.
Support diagnostics
Crash details help support identify regressions and environment-specific failures.
No credential payloads
Provider secrets are not needed for crash diagnostics and remain in the OS keychain.
Admin review
The platform includes an admin crash-report view for triage.
How it works
Typical workflow
1
Step 1
Use the app normally.
2
Step 2
If a crash or error occurs, include what you were doing when contacting support.
3
Step 3
Support reviews diagnostic context and release version.
4
Step 4
Install the next patch release if a fix is shipped.
Options
Important details
Useful context
Version, platform, and non-secret app context are more useful than screenshots alone.
Manual QA still matters
Users should report reproducible steps for file-operation bugs.
Privacy boundary
Do not send provider passwords or API keys to support.