Architecture: How minimal should the VSCode Extension MVP be?

Documentation for Sessions

🏗️ Architecture: How minimal should the VSCode Extension MVP be?

Date: 2026-01-30
Time: 12:28:39 UTC
Session: editor2-75.4
Agent: angular
Confidence: 90%
Status: ✅ Documented


📋 Decision Context

Question:

How minimal should the VSCode Extension MVP be?

Task: Not specified


🎯 Decision Made

Chosen:

Status-bar-only MVP with WebSocket connection for notifications, quick pick menu for status view, no webviews or complex UI. Heavy lifting delegated to browser-based Control Center.

Options Considered:

  1. Status-bar-only MVP
  2. Full webview dashboard
  3. Tree view sidebar
  4. No extension needed

💭 Reasoning

  1. MCP already handles agent communication - extension shouldn't duplicate. 2) VSCode webviews are complex and slow to develop. 3) Status bar provides at-a-glance info without context switching. 4) Quick pick is native VSCode pattern, consistent UX. 5) Opening Control Center in browser gives full functionality without VSCode complexity.

📁 Files Involved


🔗 Related


Auto-generated by MCP Smart Consolidation