{"version":"2.1.286","anchor":"plugins-sync-telemetry-and-mcp-auto-background-skipping","canonical_anchor":"plugins-sync-telemetry-and-mcp-auto-background-skipping","heading":"MCP tool calls can skip automatic backgrounding in some sessions","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/plugins-sync-telemetry-and-mcp-auto-background-skipping","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### MCP tool calls can skip automatic backgrounding in some sessions\n\nUnder a new condition, an MCP tool call no longer gets a timer for moving itself to the background, and plugin sync logs two more details\n\n**Unclear.** It is not clear which sessions meet the condition that turns off automatic backgrounding.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When Claude calls one of those tools, Claude Code can set a timer that moves a long-running call into the background so the conversation is not held up. There is now a condition under which that timer is left unset for the call, so it is not moved to the background automatically.\n\nTwo other changes sit alongside this:\n\n- The record Claude Code logs when plugin syncing skips MCP servers now carries two extra details, where before it carried none.\n\n- The server discovery that runs when the working folder changes, and during plugin sync, now passes along an extra filter.\n\n**Why**\n\nIn the sessions where the new condition applies, a slow MCP tool call may stay in the foreground until it finishes instead of moving to the background.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}