{"version":"2.1.221","anchor":"mcp-tasks-use-raw-requests-instead-of-the-experimental-clien","canonical_anchor":"mcp-tasks-use-raw-requests-instead-of-the-experimental-clien","heading":"MCP tasks use raw requests instead of the experimental client helpers","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-tasks-use-raw-requests-instead-of-the-experimental-clien","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP tasks use raw requests instead of the experimental client helpers\n\nMCP task results and cancellations now use standard requests instead of an experimental helper.\n\n**What**\n\nTask result fetching and cancellation no longer depend on the experimental client surface.\n\n**Details**\n\n- both now call `e.request({ method: \"tasks\/result\", ... })` and `{ method: \"tasks\/cancel\", ... }` with explicit result schemas\n- replaces calls into `experimental.tasks`\n\n**Evidence**\n\n`tasks\/cancel`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}