[Feat] Add privacy-safe diagnostics reports - #1172
Draft
zoomote[bot] wants to merge 2 commits into
Draft
Conversation
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds
Zoo Code: Create Diagnostics Reportto the Command Palette for troubleshooting blank webviews, missing history, and failed task or subtask navigation. The extension creates a bounded structural report covering version and environment metadata, provider and task state, navigation events, task persistence integrity, webview hydration and sequence state, theme colors, and fingerprint-only runtime errors.The report opens locally and is copied to the clipboard for review. Task identifiers are report-local pseudonyms, failed navigation targets are inspected, and conversation content, secrets, identity, file paths, raw logs, and other sensitive payloads are excluded.
Why this change was made
Existing diagnostics were limited to specific subsystems or depended on a healthy webview. This provides one privacy-safe collection path that remains usable when the Zoo Code UI itself cannot show useful troubleshooting information.
Impact
Users can quickly share a valid JSON report without uploading data automatically or exposing conversation content. Collection remains useful with no active task, a nonresponsive webview, corrupt or oversized persistence files, and partial collection failures.
Related PRs