{"version":"2.1.301","anchor":"mcp-call-and-dispatch-signatures-gain-an-extra-argument","canonical_anchor":"mcp-call-and-dispatch-signatures-gain-an-extra-argument","heading":"Background tasks pass more detail when they wake Claude up","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/mcp-call-and-dispatch-signatures-gain-an-extra-argument","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Background tasks pass more detail when they wake Claude up\n\nA background task that wakes Claude now passes along where its prompt came from and details about its notices\n\n**Unclear.** It is not clear what the added notice details or the extra MCP information change for users.\n\n**What**\n\nWhen a background task finishes, it can send Claude a prompt to wake it up. Before, that prompt was always labelled as a task notification. It now passes along where the prompt really came from, plus details about the notices it carries, such as their lengths, which ones belong to the task and which runs they came from.\n\nClaude Code also passes one more piece of information when it processes results from MCP tools, which are tools provided by outside programs.\n\n**Why**\n\nPrompts from background tasks can now say where they came from instead of carrying a fixed label.\n\n- Flag `tengu_mcp_connect_timeout_retry`: Not enough to say (read for one account on one subscription tier against v2.1.301; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}