{"version":"2.1.222","anchor":"active-mcp-server-tool-markers-are-cleared-on-conversation-r","canonical_anchor":"active-mcp-server-tool-markers-are-cleared-on-conversation-r","heading":"Active MCP server\/tool markers are cleared on conversation reset","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/active-mcp-server-tool-markers-are-cleared-on-conversation-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Active MCP server\/tool markers are cleared on conversation reset\n\nErrors after a conversation reset are no longer mislabelled with the MCP server and tool from a previous turn.\n\n**What**\n\nStale MCP attribution no longer survives a conversation reset, so a later error or event is not tagged with the server and tool from a previous turn.\n\n**Details**\n\n- The query loop's tool-state object gained an `onReset` hook\n- The hook calls a new helper that clears `activeMcpServer` and `activeMcpTool` on the options object, guarded by try\/catch\n- The same helper is also invoked at the start of the API loop\n\n**Evidence**\n\n`activeMcpServer`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}