Baike.dev
Log in
Back to tool/Back to issues
#20675·cherry-studio

[Feature]: Support for Server-side Agent Integration: Hermes, Stella, and OpenAI

Author: kangfenmaoCreated Sep 17, 2026Updated Sep 17, 2026

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 is a product requirement or preliminary research.

Is your feature request related to an existing issue?

Need to make Cherry Studio become the desktop interaction entry point for server-side Agents, use locally deployed or remotely deployed Agents in the existing Agent conversation list, and explore letting them call client-side local tools.

Desired Solution

  • Research the actual API and conversation capabilities of Hermes, Stella, and OpenAI server-side Agents, clarify the first batch of integration scope.
  • Users can add server-side Agents just like adding local Agents, and initiate and continue conversations in the Agent conversation list.
  • Also consider configuration for local deployment addresses and remote service addresses.
  • Research how to provide client-side local tools for server-side Agents to call, clarify protocols, authorization boundaries, and limitations when not supported; do not assume existing APIs already support tool callbacks.
  • First establish integration capabilities in the community edition, providing a foundation for subsequent enterprise edition reuse.

Suggested acceptance criteria:

  • Form a comparison of API capabilities and limitations for the three types of services, clarify the specific products/APIs corresponding to OpenAI.
  • Complete the process of adding, conversing, and error feedback for the first batch of server-side Agents.
  • Local tool calling forms a verifiable plan, or clearly records parts not supported by current services.
  • Users can distinguish between local Agents and server-side Agents.

Alternative Solutions

Existing CodeMate runtime integration or Agent presets can reuse some experience, but cannot replace the connection and conversation capabilities of server-side Agents.

Additional Information

Meeting discussion time: 00:55:06–00:58:01. The meeting agreed to proceed in parallel; this issue is categorized under v2.2.0 according to subsequent arrangements.

Related issues:

  • #18806: Hermes CodeMate engine integration, different from server-side connection scenarios.
  • #19794: Hermes Agent built-in presets, does not include server-side Agent integration.
  • #17908: ACP integration with other Agents, can serve as protocol research reference.

Unified scheduling across Agents and "butler Agent" will be researched separately, not as a prerequisite for this first delivery.

Basis: 2026-09-17 Community Edition internal requirements sync meeting. Acceptance items are suggestions organized based on meeting goals. Relevant GitHub issues have been searched and linked above; Discussions and latest release versions 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 对话列表中使用本地部署或远程部署的 Agent，并探索让其调用客户端本地工具。

Desired Solution

  • 调研 Hermes、Stella 和 OpenAI 服务端 Agent 的实际 API 与会话能力，明确首批接入范围。
  • 用户能够像添加本地 Agent 一样添加服务端 Agent，并在 Agent 对话列表中发起和继续对话。
  • 同时考虑本地部署地址与远程服务地址的配置。
  • 调研如何将客户端本地工具提供给服务端 Agent 调用，明确协议、授权边界及不支持时的限制；不预设现有 API 已支持工具回调。
  • 先在社区版建立接入能力，为后续企业版复用提供基础。

建议验收标准：

  • 形成三类服务的 API 能力与限制对照，明确 OpenAI 对应的具体产品/API。
  • 完成首批服务端 Agent 的添加、会话和错误反馈流程。
  • 本地工具调用形成可验证的方案，或明确记录当前服务不支持的部分。
  • 用户能够区分本地 Agent 与服务端 Agent。

Alternative Solutions

已有 CodeMate runtime 集成或 Agent 预设可以复用部分经验，但不能替代服务端 Agent 的连接和会话能力。

Additional Information

会议讨论时间：00:55:06–00:58:01。会议同意可并行推进；本 issue 按后续安排归入 v2.2.0。

关联 issue：

  • #18806：Hermes CodeMate 引擎集成，与服务端连接场景不同。
  • #19794：Hermes Agent 内置预设，不包含服务端 Agent 接入。
  • #17908：ACP 接入其他 Agent，可作为协议调研参考。

跨 Agent 的统一调度与“管家 Agent”另行调研，不作为本条首期交付前提。

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

Source: CherryHQ/cherry-studio

View original on GitHubView discussion on GitHub