{"version":"2.1.318","anchor":"mcp-task-outcome-unknown-message-for-connector-changed","canonical_anchor":"mcp-task-outcome-unknown-message-for-connector-changed","heading":"Clearer warning when a task's connector has been replaced","tier":"notice","area":"Connectors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/mcp-task-outcome-unknown-message-for-connector-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Clearer warning when a task's connector has been replaced\n\nIf a connector changed under an unfinished MCP task, Claude is told retrying would reach the new connector and to ask you first\n\n**What**\n\nWhen Claude Code cannot tell whether an MCP tool task finished, it shows a notice. MCP is a way to connect outside services, called connectors, that give Claude extra tools. Before, the notice always said calling the tool again may repeat the work.\n\nWhen the connector has changed, the notice now says: \"Calling the tool again would reach the connector that has the name now, so ask the user before calling it again.\" It leaves out the task's last status text in that case.\n\n**Why**\n\nIf a connector was swapped for a different one with the same name, retrying could send the work somewhere else, so Claude is told to check with you first.\n\n- Area: Connectors\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}