This issue was translated automatically.
Issue Checklist
Platform
macOS
Version
v2.0.7
Bug Description
When launching DeepSeek Harness in Code Mate, the list allows selecting cherryin Enterprise + GPT-5.6 Luna. After clicking "Launch", it fails immediately with a toast:
Provider 934f5cb6-afac-4bb5-91dd-9fd5bc0eacc6 must be used through the Unified Gateway for DeepSeek Harness
934f5cb6-... is the internal ID of the enterprise provider, not a model ID. There's already a "Unified Gateway" card at the top of the same page, but the error shows raw English text with a UUID, without guiding users to use the Unified Gateway.
DSH version shows as v0.1.0-rc.6.
Steps To Reproduce
- Open Cherry Studio v2.0.7 → Code Mate.
- Select DeepSeek Harness.
- In model provider, select cherryin Enterprise, and model GPT-5.6 Luna (do not click "Unified Gateway").
- Click "Launch".
- See the above toast, DSH does not start.
Expected Behavior
At least one of the following should be implemented:
- Combinations of "reasoning model + provider that doesn't support developer role" should not appear in the launchable list; or
- Automatically route through the Unified Gateway when launching; or
- Show a localized, actionable prompt: "Please launch this model through the Unified Gateway", instead of throwing an internal provider UUID.
Selecting and clicking launch should not fail first and then let the user guess.
Relevant Log Output
Provider 934f5cb6-afac-4bb5-91dd-9fd5bc0eacc6 must be used through the Unified Gateway for DeepSeek Harness
Additional Context
When launching, only clicking "Unified Gateway" results in mode: 'gateway', while clicking a specific provider uses direct:
// src/renderer/pages/code/hooks/useDeepSeekHarnessController.ts
mode: isApiGatewayProviderId(enabledProvider.id) ? 'gateway' : 'direct'
In direct mode, resolveDeepSeekHarnessEndpoint() checks: when reasoning models use OpenAI-compatible endpoints, DSH/pi-ai requires the developer role. The default is apiFeatures.developerRole === false. Enterprise cherryin generally has this default value as well, and lacks an Anthropic fallback endpoint, so it throws:
throw new Error(`Provider ${provider.id} must be used through the Unified Gateway for DeepSeek Harness`)
However, Code Mate's DSH provider filter (CLI_TOOL_PROVIDER_MAP[DEEPSEEK_HARNESS]) only checks: non-pure login, has API Key, has OpenAI/Anthropic endpoints, but does not check this launch hard rule.
So the UI thinks it can launch, but the main process rejects it. Current workaround: select "Unified Gateway", then select the same GPT-5.6 Luna.
Original Content
Issue Checklist
Platform
macOS
Version
v2.0.7
Bug Description
Code Mate 里启动 DeepSeek Harness 时,列表允许选择 cherryin企业版 + GPT-5.6 Luna,点「启动」后立刻失败,toast:
Provider 934f5cb6-afac-4bb5-91dd-9fd5bc0eacc6 must be used through the Unified Gateway for DeepSeek Harness
934f5cb6-... 是该企业版服务商的内部 id,不是模型 id。同一页上方已经有「统一网关」卡片,但报错是原始英文 + UUID,没有引导改点统一网关。
DSH 版本显示为 v0.1.0-rc.6。
Steps To Reproduce
- 打开 Cherry Studio v2.0.7 → Code Mate。
- 选择 DeepSeek Harness。
- 在模型服务商里选 cherryin企业版,模型选 GPT-5.6 Luna(不要点「统一网关」)。
- 点「启动」。
- 看到上述 toast,DSH 未启动。
Expected Behavior
下面至少做到一件:
- 这种「reasoning 模型 + 服务商不支持 developer role」的组合不要出现在可启动列表里;或
- 启动时自动改走统一网关;或
- 用本地化、可操作的提示:「该模型请通过统一网关启动」,而不是抛内部 provider UUID。
选中并点启动不应先失败再让用户猜。
Relevant Log Output
Provider 934f5cb6-afac-4bb5-91dd-9fd5bc0eacc6 must be used through the Unified Gateway for DeepSeek Harness
Additional Context
启动时只有点「统一网关」才是 mode: 'gateway',点具体服务商走 direct:
// src/renderer/pages/code/hooks/useDeepSeekHarnessController.ts
mode: isApiGatewayProviderId(enabledProvider.id) ? 'gateway' : 'direct'
直连在 resolveDeepSeekHarnessEndpoint() 里会检查:reasoning 模型走 OpenAI 兼容端点时,DSH/pi-ai 需要 developer role。默认 apiFeatures.developerRole === false。企业版 cherryin 一般也是这个默认值,又没有 Anthropic 备用端点,于是抛:
throw new Error(`Provider ${provider.id} must be used through the Unified Gateway for DeepSeek Harness`)
但 Code Mate 的 DSH 服务商过滤(CLI_TOOL_PROVIDER_MAP[DEEPSEEK_HARNESS])只看了:非纯登录、有 API Key、有 OpenAI/Anthropic 端点,没有检查这条启动硬规则。
所以 UI 认为可以启动,主进程再拒绝。当前绕过:改选「统一网关」,再选同一套 GPT-5.6 Luna。
Issue Checklist
Platform
macOS
Version
v2.0.7
Bug Description
When launching DeepSeek Harness in Code Mate, the list allows selecting cherryin Enterprise + GPT-5.6 Luna. After clicking "Launch", it fails immediately with a toast:
934f5cb6-...is the internal ID of the enterprise provider, not a model ID. There's already a "Unified Gateway" card at the top of the same page, but the error shows raw English text with a UUID, without guiding users to use the Unified Gateway.DSH version shows as
v0.1.0-rc.6.Steps To Reproduce
Expected Behavior
At least one of the following should be implemented:
Selecting and clicking launch should not fail first and then let the user guess.
Relevant Log Output
Provider 934f5cb6-afac-4bb5-91dd-9fd5bc0eacc6 must be used through the Unified Gateway for DeepSeek HarnessAdditional Context
When launching, only clicking "Unified Gateway" results in
mode: 'gateway', while clicking a specific provider usesdirect:In direct mode,
resolveDeepSeekHarnessEndpoint()checks: when reasoning models use OpenAI-compatible endpoints, DSH/pi-ai requires thedeveloperrole. The default isapiFeatures.developerRole === false. Enterprise cherryin generally has this default value as well, and lacks an Anthropic fallback endpoint, so it throws:However, Code Mate's DSH provider filter (
CLI_TOOL_PROVIDER_MAP[DEEPSEEK_HARNESS]) only checks: non-pure login, has API Key, has OpenAI/Anthropic endpoints, but does not check this launch hard rule.So the UI thinks it can launch, but the main process rejects it. Current workaround: select "Unified Gateway", then select the same GPT-5.6 Luna.
Original Content
Issue Checklist
Platform
macOS
Version
v2.0.7
Bug Description
Code Mate 里启动 DeepSeek Harness 时,列表允许选择 cherryin企业版 + GPT-5.6 Luna,点「启动」后立刻失败,toast:
934f5cb6-...是该企业版服务商的内部 id,不是模型 id。同一页上方已经有「统一网关」卡片,但报错是原始英文 + UUID,没有引导改点统一网关。DSH 版本显示为
v0.1.0-rc.6。Steps To Reproduce
Expected Behavior
下面至少做到一件:
选中并点启动不应先失败再让用户猜。
Relevant Log Output
Provider 934f5cb6-afac-4bb5-91dd-9fd5bc0eacc6 must be used through the Unified Gateway for DeepSeek HarnessAdditional Context
启动时只有点「统一网关」才是
mode: 'gateway',点具体服务商走direct:直连在
resolveDeepSeekHarnessEndpoint()里会检查:reasoning 模型走 OpenAI 兼容端点时,DSH/pi-ai 需要developerrole。默认apiFeatures.developerRole === false。企业版 cherryin 一般也是这个默认值,又没有 Anthropic 备用端点,于是抛:但 Code Mate 的 DSH 服务商过滤(
CLI_TOOL_PROVIDER_MAP[DEEPSEEK_HARNESS])只看了:非纯登录、有 API Key、有 OpenAI/Anthropic 端点,没有检查这条启动硬规则。所以 UI 认为可以启动,主进程再拒绝。当前绕过:改选「统一网关」,再选同一套 GPT-5.6 Luna。