{"version":"2.1.286","anchor":"mcp-calls-can-be-moved-to-background-without-a-timer","canonical_anchor":"mcp-calls-can-be-moved-to-background-without-a-timer","heading":"Some MCP tool calls can move to the background without a timer","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/mcp-calls-can-be-moved-to-background-without-a-timer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Some MCP tool calls can move to the background without a timer\n\nAn MCP tool call can now be moved to the background even when no auto-background timer is set, if a new check says the call can be moved\n\n**Unclear.** It is not clear what the new check looks at to decide that a call can be moved.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. A long-running call to one of those tools can be moved to the background so the conversation is not held up. Before, this only happened when a timer for it was set above zero. Now it can also happen with no timer, when a new check says the call can be moved. That check takes into account whether the session is non-interactive and whether the call was made from inside another call.\n\n**Why**\n\nSome MCP tool calls may now run in the background even if you never set an auto-background timer.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}