Proposal: optional authenticated MCP web-evidence workflow (Baizhi)
还没有人认领这个 Issue。
评估
调研方向
Read yaml_instance/deep_research_v1.yaml and the existing mcp_remote implementation, then inspect the workflow-list and Launch entry points. The proposal asks whether this credential-specific workflow is in scope, not for a defined implementation; first seek maintainer guidance on location and validation. If approved, done would include the optional YAML and English/Chinese setup instructions, plus the proposed host, credential, error, cleanup, and exposure checks.
由索引模型根据 Issue 内容生成。
描述
Disclosure: this is a vendor-affiliated proposal for Baizhi Cloud. I would like to check whether a small, optional DevAll 2.0 workflow is within the project's contribution scope.
For users who already have a Baizhi account, the proposed workflow would collect public web evidence and produce a short, source-linked comparison or fact-check. The current deep_research_v1.yaml uses the in-repo web functions, whose search and page-reading implementations use Serper and Jina. This would be an alternative using the user's existing Baizhi credentials, rather than a replacement for that workflow or a new vendor-specific Python provider.
The proposed addition is yaml_instance/web_evidence_baizhi.yaml, with short English and Chinese setup instructions:
- An evidence-collection agent actually binds remote MCP tools for search, page reading and structured extraction. It should retain source URLs, distinguish quoted page evidence from inference, and report unavailable information instead of inventing it.
- A separate review agent checks the collected evidence and produces the final answer; it does not need another remote tool binding.
- The YAML contains environment-variable references only. Selecting and launching this workflow is optional; existing workflows remain usable without a Baizhi key.
The connection fragment for the collection agent would reuse the existing implementation:
tooling:
- type: mcp_remote
prefix: baizhi
config:
server: https://agent-toolkit.app.baizhi.cloud/mcp
headers:
Authorization: Bearer ${BAIZHI_API_KEY}
timeout: 30
The public integration documentation documents Streamable HTTP/Bearer authentication and websearch_search, web_scrape, and web_extract. Actual argument schemas would come from MCP discovery. A least-privilege key should be configured by the operator, outside the committed workflow. This is not a claim that prompts restrict server-side permissions.
A Baizhi account and the user's own key are required; calls may consume paid credits. Tool arguments go to the hosted service and returned evidence may go to the configured model. The public repository contains integration materials, not the hosted backend source. The proposed example is for public, non-sensitive research inputs.
I have statically traced the current main configuration interpolation, Streamable HTTP headers, tool discovery/call and result handling, and the workflow-list/Launch entry. I have not run a ChatDev host/GUI or live Baizhi/model test. Before any implementation PR, verification would need to cover the actual host with a synthetic MCP service, missing/invalid credentials, errors and cleanup, and inspect logs/artifacts for credential exposure. No compatibility or production-success claim is intended at this stage.
Would this optional, credential-specific workflow be useful and acceptable in yaml_instance/, or would you prefer another contribution location? I would also welcome guidance on the expected validation for such a workflow. I noted the functional naming guidance in #555, the requirement for real crawling/tool execution in #561, and the preference for reusing generic abstractions in #594; the proposal follows those boundaries.
- 主要语言
- Python
- 星标
- 34.5k
- 派生
- 4.3k
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
OpenBMB/ChatDev 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 76/100
-
CodeReviewModification never shows the programmer the six review regulations, so fixes are made blind to the checklist they are re-reviewed against可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 1/5 1-3 小时 新手友好度 78/100
-
难度 1/5 1 小时以内 新手友好度 85/100
-
FunctionManager silently drops tool modules containing dataclasses with postponed annotations可能已有人在做 @inchang-ing 于 14 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 72/100
-
难度 4/5 3-5 天 新手友好度 35/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 1/5 1 小时以内 新手友好度 62/100
-
难度 1/5 1 小时以内 新手友好度 70/100
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
topoteretes/cognee#5773 ·
维护者通常 1 天内回复
-
MiKTeX: a failed build reports no errors because texify --quiet switches the log to file:line: style未关闭
难度 2/5 1-3 小时 新手友好度 74/100
SublimeText/LaTeXTools#1718 ·