{"version":"2.1.296","anchor":"mcp-background-task-result-text-quiet-chat-caveat","canonical_anchor":"mcp-background-task-result-text-quiet-chat-caveat","heading":"Claude can warn that a background MCP task's result waits for your next message","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/mcp-background-task-result-text-quiet-chat-caveat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Claude can warn that a background MCP task's result waits for your next message\n\nFor some background MCP tasks, Claude is told the result may only arrive after you send another message, and not to promise to report back\n\n**Unclear.** It is not clear when Claude Code uses this wording rather than the earlier note.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. Some MCP tools start a task that keeps running on the server. Under a certain condition, the note Claude gets when such a task starts now says:\n\n- the result may not be fetched until you send another message\n\n- Claude should not tell you it will report back when the task is done\n\n- Claude should tell you that you can send any message to check on it\n\nBefore, the note said the result would arrive as a task notification.\n\n**Why**\n\nThis changes what Claude tells you about background MCP tasks. Instead of waiting for an update that may not come on its own, you know to send a message to see the result.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}