Skip to content

[Feat] Add privacy-safe diagnostics reports - #1172

Closed
ghost wants to merge 2 commits into
mainfrom
feature/diagnostics-report-2lfdqdv5ogn3y
Closed

ghost wants to merge 2 commits into
mainfrom
feature/diagnostics-report-2lfdqdv5ogn3y

Conversation

@ghost

@ghost ghost commented Aug 6, 2026 •

Copy link
Copy Markdown

Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

Adds Zoo Code: Create Diagnostics Report to 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

@ghost ghost changed the title [Feat] Create privacy-safe diagnostics reports [Feat] Add privacy-safe diagnostics reports Aug 6, 2026
@github-actions

github-actions Bot commented Aug 29, 2026 •

Copy link
Copy Markdown
Contributor

Review status

Thanks for contributing. This comment tracks the review sequence and the next action.

Current step: Resolve the merge conflicts. The review sequence resumes after the branch is mergeable.

Review-state labels are managed by this workflow; do not edit them manually. community-approved is managed the same way — do not add or remove it manually. It signals a fresh community code approval for the current head as an advisory priority only; maintainer review is still required.

@github-actions github-actions Bot added has-conflicts PR has merge conflicts with the base branch and removed has-conflicts PR has merge conflicts with the base branch labels Aug 30, 2026
@github-actions github-actions Bot added has-conflicts PR has merge conflicts with the base branch and removed has-conflicts PR has merge conflicts with the base branch labels Sep 11, 2026
@github-actions

Copy link
Copy Markdown
Contributor

This PR has been awaiting author changes for 14 days and will be automatically closed in 7 days. Please address the review comments or leave a comment if you need more time.

@github-actions

Copy link
Copy Markdown
Contributor

Closing due to author inactivity after requested changes. Feel free to reopen once the requested changes have been addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-author PR is waiting for the author to address requested changes has-conflicts PR has merge conflicts with the base branch stale-awaiting-author PR is stale while waiting for requested author changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant