Skip to content

feat(desktop): simplify Diagnostics to a status line and Copy report - #7413

Merged
reachjalil merged 2 commits into
devfrom
feat/simpler-desktop-diagnostics
Nov 14, 2026
Merged

reachjalil merged 2 commits into
devfrom
feat/simpler-desktop-diagnostics

Conversation

@reachjalil

Copy link
Copy Markdown
Member

What is this about?

Settings → Advanced → Diagnostics in the desktop app, the screen "Run diagnostics" opens. It now shows one status line, the app version and a Copy report button.

What problem does it solve?

Someone who hits a problem wants to know what is wrong and send us something we can read. The section answered with about twenty rows of internal state, and its copy button left out the app version and the logs.

What was the situation before?

"Agent access diagnostics" listed rows such as Desired revision and Plugin canaries. Nothing was checked until you pressed Refresh, and "Copy sanitized diagnostic" copied only the Cloud tools state.

How is this implemented?

  • advanced-diagnostics-section.tsx replaces the old section: status, versions, Check again, Copy report, and the old rows inside a closed "Technical details".
  • diagnostics-summary.ts turns the health result into one plain line, reusing cloudMcpDisplaySummary.
  • settings-route.tsx copies the command palette's "Copy diagnostics" report (buildDiagnosticsBundleJson), with the check result included.
  • The check runs once when a signed-in person opens the page.

What else changed?

  • The section is called "Diagnostics" in settings search and in the hints that point to it.
  • evals/worlds/account-diagnostics.ts grants clipboard access so the proof can read what was copied.

Release note

Settings → Advanced → Diagnostics now tells you in one line whether your connected tools work, with the app version and a Copy report button for sharing with support.

Evidence

evals/proofs/diagnostics-copy-report.proof.test.ts — before: about twenty rows of internal state behind a Refresh button; after: one status line, the versions and Copy report, with the rows closed under Technical details.

Design: P1, P2, P3, S1, S3, C6

Run diagnostics opened a section in Settings > Advanced that listed about
twenty rows of internal state, waited for a Refresh click before checking
anything, and copied only the Cloud tools state.

Show one plain status line, the app and engine versions, and a Copy report
button. The check runs once when a signed-in person opens the page. Copy
report copies the same sanitized report as the command palette's "Copy
diagnostics", with the result of the check included. The previous rows and
the health JSON stay available under a closed "Technical details".

The section is renamed Diagnostics in settings search and in the hints that
point to it. Developer mode still opens the Debug page.

Signed-off-by: Jalil <reachjalil@gmail.com>
@vercel

vercel Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
openwork-app Ready Ready Preview Nov 14, 2026 1:02am UTC
openwork-diagnostics Error Error Nov 14, 2026 1:02am UTC
2 Skipped Deployments
Project Deployment Actions Updated
openwork-den Ignored Ignored Preview Nov 14, 2026 1:02am UTC
openwork-landing Ignored Ignored Preview Nov 14, 2026 1:02am UTC

Request Review

@github-actions

github-actions Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

OpenWork evidence

Status Commit Preview Updated
🟢 Ready · evidence passed 4847465 Open preview 2026-11-14 01:05:40 UTC

Run details · Open the preview to inspect evidence and sandbox options.

Started by @reachjalil. Author evidence: these tests run the PR's own code. Not a CI verification or merge gate.

Settings can open before the workspace has a server connection. The
automatic check ran once at that moment, got no result, and never ran
again, so the section stayed on "Not checked" until someone pressed
Check again.

Wait for the connection before the one automatic check, say so while
waiting, and keep Check again disabled until it can run. The proof now
accepts any finished result of the check.

Signed-off-by: Jalil <reachjalil@gmail.com>

This branch had an error being deployed

1 failed (outdated) and 4 active (2 outdated) deployments
Evidence / PR 7413 — 48474654 Deployed Nov 14, 2026 by github-actions[bot]
Preview – openwork-app — 48474654 Deployed Nov 14, 2026 by vercel[bot]
Preview – openwork-landing — 930c465b Deployed Nov 14, 2026 by vercel[bot]
Preview – openwork-den — 930c465b Deployed Nov 14, 2026 by vercel[bot]
Preview – openwork-diagnostics — 930c465b Deployed Nov 14, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant