{"version":"2.1.247","anchor":"mcp-tasks-are-refused-for-subagents-and-non-interactive-runs","canonical_anchor":"mcp-tasks-are-refused-for-subagents-and-non-interactive-runs","heading":"MCP tasks are refused for subagents and non-interactive runs","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/mcp-tasks-are-refused-for-subagents-and-non-interactive-runs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### MCP tasks are refused for subagents and non-interactive runs\n\nMCP background tasks are hard-blocked for subagents and non-interactive runs, with no setting.\n\n**What**\n\nWhere the MCP task pathway exists, it is hard-blocked whenever the tool call comes from a subagent or from a non-interactive session. There is no setting; the block is wired into the call itself.\n\n**Details**\n\n- Task polling now cancels the task on the server if the local record stops being in the running state.\n- The temporary files an MCP task writes alongside itself are cleaned up when it is cancelled.\n- The pathway that these rules govern is not requested anywhere in this build.\n\n**Evidence**\n\n`j.options.isNonInteractiveSession`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}