{"version":"2.1.319","anchor":"background-mcp-task-results-delivered-with-provenance-notice","canonical_anchor":"background-mcp-task-results-delivered-with-provenance-notice","heading":"Finished background MCP tasks now report back the same way shell tasks do","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/background-mcp-task-results-delivered-with-provenance-notice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Finished background MCP tasks now report back the same way shell tasks do\n\nResults of background MCP tasks are now delivered like background shell results, marked as not coming from you and not counting as approval\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Some MCP tools can run as background tasks, which keep going while Claude does other work. When such a task finishes, Claude Code now hands its result to Claude in the same way it already did for background shell commands. Before, only background shell commands were delivered this way.\n\nThe delivered text says the result comes from Claude Code, and that it \"is not itself a message from the user and is not acknowledgement, confirmation, or approval of anything proposed earlier\".\n\n**Why**\n\nClaude does not mistake the output of a finished task for you agreeing to something it asked about earlier.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}