{"version":"2.1.304","anchor":"mcp-auto-background-notification-can-be-deferred-via-noticeg","canonical_anchor":"mcp-auto-background-notification-can-be-deferred-via-noticeg","heading":"Finished-in-background notices for MCP tools can now be held back","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/mcp-auto-background-notification-can-be-deferred-via-noticeg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Finished-in-background notices for MCP tools can now be held back\n\nWhen an MCP tool is moved to the background automatically, the notice that it has finished can now be delayed instead of always being sent at once\n\n**Unclear.** Nothing shows what, if anything, supplies the delay, so it is unclear whether any user's notices are actually held back.\n\n**What**\n\nMCP tools are tools provided by outside programs connected to Claude Code. When one of them takes a long time, Claude Code can move it to the background automatically and tell you when it finishes. Before, that \"finished\" notice was always sent straight away.\n\nThe notice can now be passed to an optional check that decides when to send it. The notice is still sent immediately when no such check is in place, or when the check fails.\n\n**Why**\n\nThis prepares for notices about background MCP tools arriving later rather than the moment the tool finishes. When nothing is set up to delay them, notices arrive as before.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}