PathKeep support is metadata-first. We need enough context to debug platform, scheduler, archive, or release issues without normalizing the habit of sending private history data or secrets.
- Read TROUBLESHOOTING.md.
- Reproduce the issue once with the exact steps written down.
- Capture the diagnostics listed below.
- File the GitHub bug report template instead of opening a blank issue.
- app version
- git short SHA
- platform and installer type
- archive mode
- scheduler install state
- keyring backend and whether a convenience secret is stored
- latest run ID, audit artifact path, or remote bundle path if relevant
- whether the problem happened in browser preview, desktop dev, or a packaged release
Share these by default:
- warning text
- error codes
- run IDs
- audit artifact paths
- checksum or verification status
- sanitized screenshots
Do not share these by default:
- archive database files
- raw history exports
- master passwords
- API keys
- S3 access keys or secret access keys
- full prompt or note bodies if they contain personal browsing data not needed for the bug
PathKeep does not currently ship an automatic support-bundle exporter. The intended operator path is still manual and redacted:
- capture metadata from Settings, Schedule, Security, Audit, or Remote Backup verification
- attach only the smallest artifact needed to reproduce or confirm the issue
- prefer audit/report files over canonical archive data
If you ask a user for extra artifacts:
- explain why you need them
- ask for the narrowest possible file set
- prefer derived or audit artifacts over canonical history data
- explicitly remind the user not to send secrets