[Feature]: Research A2A / ACP Integration and Cross-Agent Collaboration

This issue was translated automatically.

Issue Checklist

• I understand that issues are for reporting problems and requesting features, not for off-topic comments, and I will provide as much detail as possible to help resolve the issue.
• I have checked the pinned issues and searched through the existing open issues, closed issues, and discussions and did not find a similar suggestion.
• I have provided a short and descriptive title so that developers can quickly understand the issue when browsing the issue list, rather than vague titles like "A suggestion" or "Stuck."
• The latest version of Cherry Studio does not include the feature I am suggesting.

Platform

Windows / macOS / Linux (desktop requirements; specific support scope to be confirmed based on the plan)

Version

No specific version specified in the meeting; this records product requirements or preliminary research.

Is your feature request related to an existing issue?

Need to evaluate Cherry Studio's protocol integration approach with other Agents, and the possibility of unified coordination between local and cloud Agents. The meeting clarified this is a low-priority exploration, and the protocol and product plan are not yet determined.

Desired Solution

• Compare A2A and ACP's applicable scenarios, available implementations, session and task state capabilities, and clarify whether they are suitable for Cherry Studio's integration goals.
• Research the minimal solution for connecting other Agents via protocol, distinguishing between local Agent and server-side Agent scenarios.
• Explore the "butler Agent" approach for coordinating multiple Agents, assigning work, and observing execution status, including cloud Agents.
• Explain limitations and issues to be resolved regarding permissions, task ownership, result reporting, and failure handling.

Research deliverables:

• Output protocol selection comparison and recommended path, or explain reasons for not adopting.
• Clarify boundaries with existing ACP integration requirements and server-side Agent integration work.
• Complete minimal validation when feasible, record validation results and unvalidated parts.
• Provide recommendations on whether to proceed with productization and subsequent breakdown.

This issue records research and does not promise a complete orchestration system or simultaneous implementation of both protocols.

Alternative Solutions

First implement direct integration through each service's own API; only introduce a general protocol or unified scheduling layer when the protocol can provide clear value.

Additional Information

Meeting discussion time: 00:57:14–00:58:01. Priority: Low; this issue is categorized under v2.2.0 based on subsequent arrangements, with the deliverable scope being research.

Related issues:

• #17908: Existing request for local Agent integration via ACP, this issue supplements protocol comparison and cross-Agent collaboration research.
• #4931: Historical A2A multi-AI discussion requirement, can serve as background reference.

Basis: 2026-09-17 Community Edition internal requirements sync meeting. Acceptance criteria are suggestions organized based on meeting objectives. Related GitHub issues have been searched and linked above; Discussions and latest release version have not been fully verified, so relevant checkboxes remain unchecked.

---

Original Content

Issue Checklist

• I understand that issues are for reporting problems and requesting features, not for off-topic comments, and I will provide as much detail as possible to help resolve the issue.
• I have checked the pinned issues and searched through the existing open issues, closed issues, and discussions and did not find a similar suggestion.
• I have provided a short and descriptive title so that developers can quickly understand the issue when browsing the issue list, rather than vague titles like "A suggestion" or "Stuck."
• The latest version of Cherry Studio does not include the feature I am suggesting.

Platform

Windows / macOS / Linux（桌面端需求；具体支持范围按方案确认）

Version

会议未指定具体版本；此条记录产品需求或前期调研。

Is your feature request related to an existing issue?

需要评估 Cherry Studio 与其他 Agent 的协议对接方式，以及统一协调本地与云端 Agent 的可能性。会议明确这是低优先级探索，协议和产品方案尚未确定。

Desired Solution

• 对比 A2A 与 ACP 的适用场景、可用实现、会话和任务状态能力，明确是否适合 Cherry Studio 的接入目标。
• 调研通过协议连接其他 Agent 的最小方案，区分本地 Agent 与服务端 Agent 的场景。
• 探索“管家 Agent”协调多个 Agent、分配工作并观察执行状态的方案，包括云端 Agent。
• 说明权限、任务归属、结果回传和失败处理方面的限制与待解决问题。

调研交付标准：

• 输出协议选型对照与推荐路径，或说明暂不采用的原因。
• 明确与已有 ACP 接入需求及服务端 Agent 接入工作的边界。
• 在可行时完成最小验证，记录验证结果和未验证部分。
• 给出是否继续产品化及后续拆分建议。

本 issue 记录调研，不承诺完整编排系统或同时实现两套协议。

Alternative Solutions

先通过各服务自身的 API 实现直接接入；只有在协议能提供明确价值时，再引入通用协议或统一调度层。

Additional Information

会议讨论时间：00:57:14–00:58:01。优先级：低；本 issue 按后续安排归入 v2.2.0，交付范围为调研。

关联 issue：

• #17908：通过 ACP 接入本地 Agent 的已有诉求，本条补充协议比较及跨 Agent 协作调研。
• #4931：历史 A2A 多 AI 讨论需求，可作为背景参考。

依据：2026-09-17 社区版内部需求同步会议。验收项是根据会议目标整理的建议。 已检索相关 GitHub issue 并在上文关联；未完整核验 Discussions 与最新发布版，因此相关检查项保留未勾选。