The Tasks extension rebuilds long-running work for a stateless world — the server decides what becomes a task

Model Context Protocol Blog·medium signal

Tasks was redesigned for the sessionless protocol: a server answers `tools/call` with a task handle, and the client drives the lifecycle through `tasks/get`, `tasks/update`, and `tasks/cancel`. The notable design choice is that the server, not the client, decides which calls get promoted to tasks — so a tool can transparently become long-running without a client-side contract change. This is the sanctioned replacement for holding a connection open across a slow tool.