Architecture: After deleting legacy session files, should MCP code be upda...

Documentation for Sessions

🏗️ Architecture: After deleting legacy session files, should MCP code be upda...

📋 Decision Context

Question:

After deleting legacy session files, should MCP code be updated to only use unified history.json?

Task: MCP Session Management System Refactor - v8.0 Update

🎯 Decision Made

Chosen:

Update all MCP code to read exclusively from sessions/history.json

Options Considered:

Keep backwards compatibility with legacy files
Fully migrate to unified history.json only

💭 Reasoning

With unified history.json as the single source of truth, all references to legacy files (sessionID.json, workspace-specific active.json and history.json) should be removed from MCP code. This eliminates confusion and ensures consistent session tracking. The MCP server runs TypeScript source directly via tsx, so changes take effect on restart.

📁 Files Involved

sessions/history.json
MCP/mcp-development-ai/src/session/session-detector.ts
MCP/mcp-development-ai/src/services/workspace-detector.ts

🔗 Related

Decision ID: dev_1768060728992_bw4fb1c
Session: 35
Workspace: editor2

Auto-generated by MCP Smart Consolidation