{"version":"2.1.248","anchor":"mcp-reconnect-errors-are-hidden-on-remote-sessions","canonical_anchor":"mcp-reconnect-errors-are-hidden-on-remote-sessions","heading":"MCP reconnect errors are hidden on remote sessions","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/mcp-reconnect-errors-are-hidden-on-remote-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### MCP reconnect errors are hidden on remote sessions\n\nOn remote sessions, MCP reconnect errors show a generic note and log the detail locally.\n\n**What**\n\nWhen you reconnect or enable\/disable an MCP server from `\/mcp` on a session whose connection persists off this machine, the underlying exception is no longer shown. You get \"Error reconnecting to <server> (detail withheld on this connection).\" and the real text is logged locally instead.\n\n**Details**\n\n- Every server name passed into user-visible text now goes through a sanitizing transform, and the completion callback is wrapped so it applies the same transform.\n- Enable\/disable failures pass a hint about whether the change persists off the machine into the failure-message builder.\n- Local sessions are unaffected. The check that selects the withheld wording is a predicate applied to the session host; which sessions it matches is not decided in this code path.\n\n**Evidence**\n\n`Error reconnecting to ${St(J)} (detail withheld on this connection).`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}