{"version":"2.1.281","anchor":"deferred-mcp-tools-from-reconnecting-servers-are-kept-in-con","canonical_anchor":"deferred-mcp-tools-from-reconnecting-servers-are-kept-in-con","heading":"Deferred MCP tools from reconnecting servers are kept in context across compaction","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/deferred-mcp-tools-from-reconnecting-servers-are-kept-in-con","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Deferred MCP tools from reconnecting servers are kept in context across compaction\n\nDeferred tools from an MCP server that is reconnecting are now kept, not dropped, when the conversation is compacted\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. Compaction is when Claude Code shortens a long conversation to save space. Before, if a tool's MCP server was reconnecting at that moment, the tool's entry could be dropped. It is now kept, carried in a separate group for tools without a deferred channel. Servers under HIPAA restrictions (a US health-privacy law) are excluded from this.\n\nThe telemetry that records tools dropped at compaction gains a `noDeferredChannel` field to tell these two cases apart.\n\n**Why**\n\nA server that briefly drops and reconnects during compaction no longer makes Claude lose track of its tools."}