🐛 Bugfix: Why are MCP session docs being written to editor2 instead of...

Date: 2026-02-07
Time: 01:03:56 UTC
Session: editor2-97.22
Agent: angular
Confidence: 98%
Status: ✅ Documented

📋 Decision Context

Question:

Why are MCP session docs being written to editor2 instead of gspace1?

Task: Fix cross-workspace session doc contamination

🎯 Decision Made

Chosen:

Fixed .mcp.json in gspace1 to point to gspace1's own MCP start-server.sh instead of editor2's

Options Considered:

• No alternatives documented

💭 Reasoning

gspace1's .mcp.json had the mcp-gograb-ai command pointing to /Users/fguijarro/developer/repos/editor2/MCP/mcp-gograb-ai/start-server.sh. Since start-server.sh resolves WORKSPACE_ROOT as 2 directories up from itself, all doc writes went to editor2. This is the root cause of the cross-workspace doc contamination. The fix is to point to gspace1's own copy of the script.

📁 Files Involved

• .mcp.json

🔗 Related

• Decision ID: dev_1770426236555_6l45och
• Session: 97
• Workspace: editor2

Auto-generated by MCP Smart Consolidation