Under the hood
Useful2 Signal0
MCP task results and cancellations now use standard requests instead of an experimental helper.
What's wrong with this entry?
Anonymous. No account, no email.
What
Task result fetching and cancellation no longer depend on the experimental client surface.
Details
- both now call
e.request({ method: "tasks/result", ... })and{ method: "tasks/cancel", ... }with explicit result schemas - replaces calls into
experimental.tasks
Evidence
tasks/cancel
Strings lifted out of the shipped bundle, so the claim above can be checked against them.