proposals: add XXXX-tasks-versioning (Tasks extension versioning & compatibility)#11
Open
thierrypdamiba wants to merge 1 commit into
Open
Conversation
Pre-submission proposal for versioning and compatibility of the Tasks extension: how peers determine they implement a compatible version of io.modelcontextprotocol/tasks, and how an implementation declares its minimum core-spec dependency — without reopening the central extension-negotiation discussion (#1848/#1849). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a pre-submission proposal to
proposals/, per @LucaButBoring's suggestion to drop it in asXXXX-tasks-versioningfor now.What it proposes
How a client and server determine they implement a compatible version of
io.modelcontextprotocol/tasks, and how an implementation declares its minimum core-spec dependency — filling the gap SEP-2133 §"Not Specified" leaves open, without reopening the central extension-negotiation discussion in #1848 / #1849.Design stance
requires.spec.minfloor live in the Tasks settings object. Minors don't gate (additive); silent-inactive by default;-32003on a hard requirement.versionfield folds into it.Status
Written proposal only — no reference implementation yet. Happy to build one in
experimental-ext-tasksif the direction is worth pursuing. Motivation is grounded in the WG's owndocs/research/mcp-agent-tools.mdand SEP-2669 (steer/pause/resume).