[Docs] Document the diagnostics report command - #22
Draft
zoomote[bot] wants to merge 1 commit into
Draft
Conversation
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
1 participant
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
Documents
zoo-code.createDiagnosticsReportin the Command Palette guide, including when to use it for blank or white webviews, missing history, and failed task or subtask navigation. The guidance explains that the generated JSON is redacted, opened locally, copied for sharing, and never uploaded automatically.Why this change was made
Users need a clear support path when the Zoo Code webview cannot expose enough information to diagnose its own failure.
Impact
The guide now tells users what structural data the report includes, which sensitive data it excludes, and to review the report before sharing it.
Screenshots
Related PRs