A tasks-capable connector cannot ask an /mcp client for input

未关闭
#1,663 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
ai, backend

调研方向

Start with the task path in McpSource, which polls tasks to completion without an McpCaller, and compare it with the non-task path that passes the caller's capabilities through. Read how the task envelope is built and how input_required is handled today, including the cancel-and-report behaviour. Done would mean a tasks-capable connector can relay input_required to an /mcp/<wsId> client and accept its tasks/update, bound to that caller the way requestState is sealed. This is design work that needs maintainer agreement on the approach first.

由索引模型根据 Issue 内容生成。

描述

needs-triage

A connector that advertises the tasks extension (io.modelcontextprotocol/tasks) cannot ask an outside /mcp/<wsId> client for input.

Every call to such a connector takes McpSource's task path, which polls to completion and carries no McpCaller: the connector sees the runtime's capabilities, not the client's, and a task that reaches input_required is cancelled and reported, because the runtime does not serve tasks/update. A connector without the extension gets the caller's capabilities and passes input_required through to the client.

Carrying the caller on the task path needs the task wire to send the client's capabilities in its envelope and the door to relay a task's input_required and the client's tasks/update, bound to the caller the way a sealed requestState is.

主要语言
TypeScript
星标
23
派生
15
平均合并
5 小时 13 分钟
30 天内合并 PR
304

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

NimbleBrainInc/nimblebrain 的其他 Issue

查看 NimbleBrainInc/nimblebrain 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。