VS Code Doctor

Diagnose editor performance from the current machine state. Do not import old observations, fixed paths, fixed extension names, fixed OS bugs, or fixed generated-directory lists into the diagnosis.

Non-Negotiables

• No hardcoded local paths. Use the user's stated workspace, discovered editor status, or explicit placeholders.
• No fixed root cause order. Rank only by fresh evidence from this run.
• No fixed extension blocklist. Treat extension names as evidence only when they appear in live output or user-provided screenshots.
• No fixed generated-directory list. Discover ignored/generated paths from the workspace, editor settings, repository metadata, or user-provided patterns.
• No fixed benefit percentages. If there is no before/after baseline, say the impact cannot be reliably quantified.
• Do not treat whole-machine load as the editor diagnosis. Record it as context, but keep conclusions and actions focused on editor evidence.
• Treat collector output as sensitive. It can expose local paths, project names, process command lines, workspace names, log paths, and extension identifiers. Redact sensitive details before sharing externally.
• No write operations by default. Do not edit settings, disable extensions, delete caches, run system defaults, change environment variables, or kill processes without explicit confirmation.

Default Simple Mode

Default to a non-technical user experience unless the user asks for details.