Triple error when compiler is not found

[timotheeguerin]

On osx this happens everytime vscode is updated or the compute restart and tries to reopen vscode automatically for some obscure reason. The PATH doesn't seem populated correctly.

But the result is 3 popup window that take a lot of space and feel spammy

[github-actions]

🎯 Issue Triage

The VSCode extension shows three redundant error popups when the TypeSpec compiler is not found — this happens on macOS when VSCode is auto-reopened after an update or compute restart, where the PATH isn't correctly populated.

Category: Bug
Area: ide

⚠️ No reproduction provided. A minimal repro would help diagnose this issue.

🔍 Analysis

• Affected component: typespec-vscode extension
• Platform: macOS (PATH population issue on VSCode auto-reopen)
• Root cause: The extension likely triggers multiple independent checks/initialization paths that each independently attempt to resolve the compiler, and all three show an error dialog when it fails. This results in 3 popup windows shown simultaneously.
• Impact: Poor UX — the repeated error popups are spammy and confusing to users.
• The PATH not being populated correctly on macOS when VSCode restarts automatically is a known macOS + Electron shell environment issue. The extension should consolidate error reporting to a single notification.

📝 Suggested next steps

• Investigate where the 3 error dialogs are triggered in packages/typespec-vscode
• Consolidate compiler-not-found error reporting to a single notification
• Consider debouncing or deduplicating startup error dialogs
• Potentially use VSCode status bar item instead of modal dialogs for non-blocking errors

Generated by Agentic Triage