{"version":"2.1.247","anchor":"long-running-mcp-tools-are-wired-to-surface-as-background-ta","canonical_anchor":"long-running-mcp-tools-are-wired-to-surface-as-background-ta","heading":"Long-running MCP tools are wired to surface as background tasks in interactive sessions","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/long-running-mcp-tools-are-wired-to-surface-as-background-ta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Long-running MCP tools are wired to surface as background tasks in interactive sessions\n\nSlow MCP tools are wired to appear as background tasks in interactive sessions.\n\n**What**\n\nThe MCP call wrapper now carries a background-task handle and the application state setter, so a slow MCP tool could show up as a task in an ordinary interactive session. Subagent calls and non-interactive sessions are excluded.\n\n**Details**\n\n- The existing auto-background delay for MCP calls is passed alongside the new handle.\n- Subagent calls are identified by the call carrying an agent id.\n- The task pathway this feeds is not requested by anything in this build.\n\n**Evidence**\n\n`disallowTasks:`\n\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}