{"version":"2.1.221","anchor":"mcp-explains-cross-session-enable-disable-drift","canonical_anchor":"mcp-explains-cross-session-enable-disable-drift","heading":"\/mcp explains cross-session enable\/disable drift","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-explains-cross-session-enable-disable-drift","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### \/mcp explains cross-session enable\/disable drift\n\n\/mcp gains clearer messages for cross-session enable\/disable conflicts and servers blocked by managed policy.\n\n**What**\n\nNew messages cover the cases where an enable or disable in one session conflicts with what another session has already done.\n\n**Details**\n\n- Distinct text for a server another session disabled, and for one another session re-enabled so your disable did not persist.\n- Separate text for a server blocked by managed policy.\n- None of these strings exist in the previous build.\n\n**Evidence**\n\n`was disabled in another session`\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}