🏗️ Architecture: What is the root cause of VSCode extension not showing real ...

Date: 2026-02-05
Time: 04:47:51 UTC
Session: editor2-91.2
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

What is the root cause of VSCode extension not showing real data and how should it be fixed?

Task: Analyze VSCode and Chrome extensions, plan enhancements

🎯 Decision Made

Chosen:

Three compounding issues: silent error swallowing in mcp-client.service.ts, no startup health check, and subtle auth surfacing. Fix by adding health check, surfacing errors in dashboard UI, and fixing signOut to clear globalState.

Options Considered:

• No alternatives documented

💭 Reasoning

Analyzed all 6+ service files and webview components. Every API call catches errors and returns empty results ([], 0, {}). Dashboard renders these as "0 decisions" instead of "Failed to load". No connectivity check on startup means the extension happily sends 4 failing requests and shows zeroes. signOut doesn't clear globalState which is the primary auth storage.

📁 Files Involved

• apps/vscode-gograb-ai/src/services/mcp-client.service.ts
• apps/vscode-gograb-ai/src/panels/main-panel.ts
• apps/vscode-gograb-ai/src/panels/webview/components/dashboard/dashboard-view.ts
• apps/vscode-gograb-ai/src/extension.ts

🔗 Related

• Decision ID: dev_1770266871855_ypbojca
• Session: 91
• Workspace: editor2

Auto-generated by MCP Smart Consolidation