{"version":"2.1.247","anchor":"mcp-long-running-task-support-is-compiled-in-but-never-reque","canonical_anchor":"mcp-long-running-task-support-is-compiled-in-but-never-reque","heading":"MCP long-running task support is compiled in but never requested","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/mcp-long-running-task-support-is-compiled-in-but-never-reque","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### MCP long-running task support is compiled in but never requested\n\nFull support for long-running MCP server tasks is compiled in but never actually requested.\n\n**What**\n\nThe MCP tool-call path gained a full implementation of long-running server tasks: registering or adopting a task, a background driver, a placeholder result while work continues, and a poller that reports progress as `Task <id> ...`. None of it runs, because the check that decides whether to ask a server for a task is compiled to always return false and the request is sent with no task option set.\n\n**Details**\n\n- The task pathway also threads a \"tasks not allowed\" parameter through the call and its retry-after-auth path.\n- The error map for listing tools learned a new case for pagination limits being exceeded, `list_pagination_exceeded`.\n- Treat this as landed but inert; nothing in this build asks a server for a task.\n\n**Evidence**\n\n`buildSep2663PlaceholderResult`\n\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}