Bugfix: Why is command-center UI not showing active tasks and agents...

Documentation for Sessions

🐛 Bugfix: Why is command-center UI not showing active tasks and agents...

📋 Decision Context

Question:

Why is command-center UI not showing active tasks and agents despite WebSocket connection working?

Task: Debug command-center UI not displaying activity

🎯 Decision Made

Chosen:

MCP tools not calling HTTP endpoints - commandCenter.taskStarted() and commandCenter.agentSpawned() are never invoked

Options Considered:

MCP tools not calling HTTP endpoints
Frontend not listening to correct events
Backend not broadcasting events
WebSocket namespace mismatch

💭 Reasoning

Backend logs show WebSocket connection established and decisions being logged, but no HTTP POST requests to /ai-api/command-center/task/start or /agent/spawn in network logs. The command-center.ts service exists and has the methods, but mcp-init.ts executeModeSelection() calls them but MCP tools are never actually triggering these in real usage. The flow requires MCP tools to explicitly call commandCenter.taskStarted() which then POSTs to backend which broadcasts via WebSocket.

📁 Files Involved

No files specified

🔗 Related

Decision ID: dev_1767903734993_c1y90j9
Session: 31
Workspace: editor2

Auto-generated by MCP Smart Consolidation