SEP-2663: Tasks Extension changedseps/2663-tasks-extension

Upstream edited this page at 29 Jul 2026 22:46 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 28 Sep 2026 22:07 UTC.

Upstream edited 29 Jul 2026 22:46 UTC

Recorded here 28 Sep 2026 22:07 UTC

Lines+13added

Lines−13removed

From line 20 where the diff opens

First seen 14 Aug 2026 this site's first read of the page

Recorded edits2to this page, all time

The whole hunk

from line 20, old and new numbered

lines

from line 20

2020 requirements.

2121</Note>

2222

23| Field | Value |

24| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

25| **SEP** | 2663 |

26| **Title** | Tasks Extension |

27| **Status** | Final |

28| **Type** | Extensions Track |

29| **Created** | 2026-04-27 |

23| Field | Value |

24| - | - |

25| **SEP** | 2663 |

26| **Title** | Tasks Extension |

27| **Status** | Final |

28| **Type** | Extensions Track |

29| **Created** | 2026-04-27 |

3030| **Author(s)** | Luca Chang ([@LucaButBoring](https://github.com/LucaButBoring)), Caitie McCaffrey ([@CaitieM20](https://github.com/CaitieM20)); on behalf of the Agents Working Group |

31| **Sponsor** | Caitie McCaffrey ([@CaitieM20](https://github.com/CaitieM20)) |

32| **PR** | [#2663](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2663) |

31| **Sponsor** | Caitie McCaffrey ([@CaitieM20](https://github.com/CaitieM20)) |

32| **PR** | [#2663](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2663) |

3333

3434***

3535

from line 968

968968

969969The experimental tasks feature in the `2025-11-25` release is **not wire-compatible** with this extension. Implementations that need to interoperate with both surfaces can shim at the SDK level by implementing the experimental and extension flows in parallel and dispatching on the negotiated protocol version and the client capability the peer declared. The following table summarizes the expected behavior for each permutation:

970970

971| Protocol Version | `tasks.*` (legacy) | `io.modelcontextprotocol/tasks` |

972| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

973| `2025-11-25` | Legacy experimental tasks per the `2025-11-25` specification. The client opts into task augmentation per request via the `task` parameter on `CallToolRequest`; the server uses `tasks/result`, `tasks/get`, `tasks/cancel`, and (where supported) `tasks/list` per that specification. This extension does not apply. | This extension is not defined under the `2025-11-25` protocol version. Servers **MUST NOT** treat this capability as enabling tasks under that protocol version; requests proceed as if the client had declared no task capability at all. |

974| `2026-06-30` | The legacy capability is not part of this extension. Servers **MUST** treat clients declaring only the legacy capability as non-declaring with respect to this extension. Servers that simultaneously support the `2025-11-25` Tasks specification alongside this extension **SHOULD** continue to permit `tasks/get` and `tasks/cancel` requests from such clients to operate on tasks created under that flow. | The canonical case. Full task lifecycle as specified in this document, with the following wire-level differences from the `2025-11-25` experimental feature:<ul><li>`tasks/result` is removed; clients calling it **MUST** receive `-32601` (Method Not Found).</li><li>The `task` parameter on `CallToolRequest` is removed; servers **MUST** ignore it (treat the field as unknown) rather than using it as an opt-in.</li><li>The `tasks.requests.*`, `tasks.cancel`, and `tasks.list` capability declarations are not part of this extension. Servers that previously advertised these **MUST** migrate to declaring `io.modelcontextprotocol/tasks`, and **MUST NOT** continue to advertise the legacy capabilities under any protocol version that includes this extension.</li></ul> |

971| Protocol Version | `tasks.*` (legacy) | `io.modelcontextprotocol/tasks` |

972| - | - | - |

975975

976976A server that returns the standard `CallToolResult` shape — i.e., never elects to create a task — remains fully spec-compliant under this extension. Clients that have negotiated the extension **MUST** handle both result shapes for any augmented request.

977977