🏗️ Architecture: What WebSocket approach should Session 75 use for multi-agen...

Date: 2026-01-30
Time: 12:51:39 UTC
Session: editor2-75.5
Agent: backend
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

What WebSocket approach should Session 75 use for multi-agent real-time communication across Chrome Extension, VSCode Extension, and Angular apps?

Task: Not specified

🎯 Decision Made

Chosen:

WebSocket Protocol Adapter - Add /ws native WebSocket endpoint that translates to Socket.io events internally

Options Considered:

1. Add native WS endpoint alongside Socket.io (duplication)
2. HTTP long-polling for extensions (poor UX)
3. Replace Socket.io with native WS everywhere (risky rewrite)
4. Socket.io + EventSource hybrid (inconsistent)
5. WebSocket-to-Socket.io Adapter (CHOSEN)

💭 Reasoning

Session 74 built Socket.io infrastructure that works for Angular apps. Chrome MV3 and VSCode extensions cannot use socket.io-client (MV3 service worker limitations, protocol incompatibility). Option E (WebSocket Adapter) preserves all existing Socket.io features (rooms, namespaces, reconnect) while enabling native WebSocket clients. Single source of truth for events, JWT auth via AuthCoreModule, future-proof for any client.

📁 Files Involved

• apis/backend-ai-api/src/app/mcp-gateway/mcp-gateway.gateway.ts
• apps/vscode-gograb-ai/src/agent-status.ts
• apps/gograb-ai-extension/background/mcp-connector.js

🔗 Related

• Decision ID: dev_1769777495851_9wh902a
• Session: 75
• Workspace: editor2

Auto-generated by MCP Smart Consolidation