Claude Code v2.1.221 ·
MCP task polling uses plain protocol requests instead of the experimental tasks client
MCP task polling now uses plain protocol calls instead of an experimental client path.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.221,
Internal ChangesSection of the release
What
getTask, getTaskResult and cancelTask no longer go through the SDK's experimental tasks namespace.
Details
- replaced by direct requests for "tasks/get", "tasks/result" and "tasks/cancel"
- each request carries an explicit result schema
Evidence
{ method: "tasks/cancel", params: { taskId: i } }
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.221 →
