Implement task-augmented requests#5
Draft
hunner wants to merge 2 commits into
Draft
Conversation
Collaborator
|
rad |
hunner
force-pushed
the
hunner/mcp-task-augment
branch
from
d00f263 to
012f640
Compare
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
2 participants
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.
As per https://modelcontextprotocol.io/specification/2025-11-25/basic/utilities/tasks#protocol-messages
This allows for async tool calls that avoid timeouts while waiting for approval.
The way it works is that the mcp spec protocol is negotiated then persisted via
MCP-Session-Idas per the spec in a kv store (in memory or redis), and if 2025-11-25 is supplied then harnesses are coerced to use tasks by listing tools withtaskSupport: required, but making it optional for older protocols.