[Feature]: Support Pi Plugin Discovery, Installation, and Management

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?

After Pi becomes the primary Agent runtime, users need to conveniently discover and install Pi ecosystem plugins to extend Agent capabilities, rather than relying solely on manual local extension configuration.

Desired Solution

• Research and integrate available plugin sources from the Pi ecosystem, providing user-accessible search, installation, and installed plugin management entry points.
• Clarify compatibility requirements and necessary configurations between plugins and the Pi runtime, so users know which runtime a plugin is compatible with.
• Reuse existing plugin or extension loading capabilities, clarifying how to take effect in Pi Agent after installation.
• Allow functionality differences across different runtimes; aligning plugin capabilities with runtimes like Claude is not a prerequisite.
• Explore the workflow for Agents to write and test Pi plugins as a future extension direction, not required for the initial implementation.

Suggested acceptance criteria:

• Users can discover and install a compatible Pi plugin.
• Installed plugins can be viewed and managed, with necessary configurations and activation conditions clearly stated.
• Plugins can be actually used in Pi Agent; provide clear feedback when incompatible or loading fails.
• Clarify third-party plugin execution permissions and user confirmation methods.

Alternative Solutions

Manual loading of user local Pi configurations and extensions can serve as a basic capability, but a user-facing discovery, installation, and management experience is still needed.

Additional Information

Meeting discussion time: 00:32:31–00:33:19. Added during the discussion of Pi as the default runtime; this issue is categorized under v2.2.0 based on subsequent arrangements.

Related issues:

• #20331: Load user native Pi configurations and extensions; need to coordinate implementation boundaries to avoid duplicate loading mechanism development.
• #20328: Plan for Pi as the default Agent runtime.

Basis: 2026-09-17 Community Edition internal requirements sync meeting. Acceptance items are suggestions organized based on meeting objectives. Relevant GitHub issues have been searched and linked above; Discussions and the latest release version have not been fully verified, so related 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?

在 Pi 成为主要 Agent runtime 后，需要让用户便捷地发现和安装 Pi 生态插件，扩展 Agent 能力，而不只依赖手工配置本地扩展。

Desired Solution

• 调研并接入 Pi 生态可用的插件来源，提供用户可操作的搜索、安装与已安装插件管理入口。
• 明确插件与 Pi runtime 的兼容性要求及必要配置，让用户知道插件适用于哪个 runtime。
• 复用已有插件或扩展加载能力，明确安装后如何在 Pi Agent 中生效。
• 允许不同 runtime 的功能存在差异，不将 Claude 等 runtime 的插件能力对齐作为前提。
• 探索让 Agent 编写并测试 Pi 插件的流程，作为后续扩展方向，不要求首期实现。

建议验收标准：

• 用户能发现并安装一个兼容的 Pi 插件。
• 已安装插件可查看和管理，必要配置与生效条件清晰。
• 插件可在 Pi Agent 中实际使用；不兼容或加载失败时提供明确反馈。
• 明确第三方插件执行权限及用户确认方式。

Alternative Solutions

手工加载用户本地 Pi 配置与扩展可作为基础能力，但仍需面向用户的发现、安装和管理体验。

Additional Information

会议讨论时间：00:32:31–00:33:19。在 Pi 默认 runtime 的讨论中补充提出，本 issue 按后续安排归入 v2.2.0。

关联 issue：

• #20331：加载用户原生 Pi 配置与扩展，需协调实现边界，避免重复建设加载机制。
• #20328：Pi 作为默认 Agent runtime 的规划。

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