[Feature]: runtime management

[DeJeune]

Note

This issue was translated by Claude.

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

macOS

Version

v1.7.17

Is your feature request related to an existing issue?

Need a unified place to manage runtimes (git, node, python....)

Desired Solution

Need a unified place to manage runtimes (git, node, python....)

Alternative Solutions

No response

Additional Information

No response

---

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

macOS

Version

v1.7.17

Is your feature request related to an existing issue?

需要一个地方统一管理运行时(git, node, python....)

Desired Solution

需要一个地方统一管理运行时(git, node, python....)

Alternative Solutions

No response

Additional Information

No response

[SiinXu]

Note

This comment was translated by Claude.

Current Situation:

After Windows users install the client, using Agent mode causes errors due to missing git-bash or unconfigured PATH/environment variables. Users must manually install Git and set CLAUDE_CODE_GIT_BASH_PATH, etc., which is a cumbersome process.

Pain Points:

• High barrier to first-time use, easily stuck on missing dependencies/unconfigured environment variables.
• Error messages are technical, making it difficult for ordinary users to locate and solve problems.
• Many dependencies (uv, python, node, bun, ocr, embedding, git), with unclear installation order and version requirements.

Goals:

• Users can complete "dependency check → installation → configuration → verification" with one click in the client, and Agent mode can run normally.
• Provide clear guidance, visual progress, and retry capabilities for missing dependencies.
• Reduce the first-time use failure rate.

Requirements

Use Cases:

• After installing the client for the first time, users enter Agent mode or related functions.
• The client detects missing dependencies/unsatisfied versions and prompts "one-click installation list", referring to MCP environment detection.
• Users click install, and the client automatically completes download, installation, environment variable configuration, and verification.

Requirements Scope:

Dependency Detection: uv, Python, Node.js, Bun, Git for Windows (including git-bash), [OCR dependencies] [Embedding dependencies] (specific components [to be confirmed]).
One-click Installation: Provide automatic installation for missing items (or launch official installer for silent installation).
Auto Configuration: PATH/necessary environment variables (at least including CLAUDE_CODE_GIT_BASH_PATH pointing to bash.exe).
Post-installation Verification: Run a set of "health checks" to ensure the Agent mode startup path passes.
UI: Installation list, missing status, version information, installation progress, failure reasons, retry/skip.
Logging: Installation process and failure reasons can be exported for troubleshooting.

Business Rules/Logic:

Startup/Enter Agent prerequisite check:

• If git-bash is detected as non-existent or unexecutable, block entry and guide installation/configuration.
• If installed but not in PATH: optionally "automatically fix PATH/set dedicated environment variables".

---

Original Content

现状：

Windows 用户安装客户端后，使用 Agent 模式会因缺少 git-bash 或未配置 PATH/环境变量而报错；用户需手动安装 Git 并设置 CLAUDE_CODE_GIT_BASH_PATH 等，流程繁琐。

痛点：

首次使用门槛高，容易卡在依赖缺失/环境变量未配置。
报错信息偏技术向，普通用户难以定位并解决。
依赖项较多（uv、python、node、bun、ocr、嵌入、git），安装顺序与版本要求不清晰。

目标：

用户在客户端内点击一次即可完成"依赖检查→安装→配置→验证"，Agent 模式可正常运行。
对缺失依赖给出明确引导、可视化进度与可重试能力。
降低首次使用失败率。

需求

使用场景：

首次安装客户端后，用户进入 Agent 模式或相关功能。
客户端检测到依赖缺失/版本不满足，提示"一键安装清单"，参考 MCP 环境检测。
用户点击安装，客户端自动完成下载、安装、环境变量配置与验证。

需求范围：

依赖检测：uv、Python、Node.js、Bun、Git for Windows（含 git-bash）、【OCR 依赖】【嵌入依赖】（具体组件【待确认】）。
一键安装：对缺失项提供自动安装（或拉起官方安装器静默安装）。
自动配置：PATH/必要环境变量（至少包含 CLAUDE_CODE_GIT_BASH_PATH 指向 bash.exe）。
安装后验证：运行一组"健康检查"，确保 Agent 模式启动链路通过。
UI：安装清单列表、缺失状态、版本信息、安装进度、失败原因、重试/跳过。
日志：安装过程与失败原因可导出，用于支持排障。

业务规则/逻辑：

启动/进入 Agent 前置检查：
若检测到 git-bash 不存在或不可执行，则阻断进入并引导安装/配置。
若已安装但不在 PATH：可选择"自动修复 PATH/设置专用环境变量"。

[DeJeune]

Note

This comment was translated by Claude.

This feature looks very valuable, when is it planned to start implementation?

---

Original Content

这个 feature 看起来很有价值，计划什么时候开始实现？

[cherry-ai-bot]

这个 feature request 已收到，runtime 统一管理会在后续版本中规划。

[SiinXu]

Related: #14893 — [Feature]: Bundle Portable Runtimes (uv, Git, Node) into Installer. This addresses the environment dependency pain reported here. Please follow #14893 for progress.

[SiinXu]

Covered by #14893 — Bundle Portable Runtimes (uv, Git, Node) into Installer.

[SiinXu]

Superseded by #14895 — Pluggable Capability System. This requirement is now covered as part of the unified PRD (environment dependencies + local model management + capability tools as Agent-callable tools). Closing in favor of the consolidated issue.