0.1.45 更新后第三方模型服务商全线报错(Console Go/DeepSeek/100hub/枣树)
- Dominant language
- TypeScript
- Stars
- 2.7k
- Forks
- 395
- Avg merge
- 21h 48m
- Merged PRs (30d)
- 776
Description
## 现象
更新到 0.1.45-hotfix(2026-08-12 15:17 安装)后,所有非官方模型服务商无法对话,均在会话报错横幅出现:
1. **Console Go(opencode-go)**
`Error from provider (Console Go): Upstream request failed: [invalid_request_error] Unsupported custom tool: 'exec'. Only 'apply_patch' is supported.`
2. **DeepSeek(deepseek)**
`Unsupported custom tool: 'exec'. Only 'apply_patch' is supported.`(providerId=deepseek)
3. **100hub**
`unexpected status 503 Service Unavailable: Service temporarily unavailable, url: http://127.0.0.1:63374/responses`
4. **枣树(provider-1l79y61)**
`stream disconnected before completion: [ArrayParam] [input[27].content] [array_above_max_length] Invalid 'input[27].content': array too long. Expected an array with maximum length 0, but got an array with len...`
另有 litellm 桥接层提示:
- `Responses feature is not supported by the Chat Completions bridge: tools[3].web_search`
- `Responses feature is not supported by the Chat Completions bridge: input[0].content`
## 时间线
- 15:17:57 安装 cindy-0.1.45-hotfix.zip,15:18:14 完成重启
- 15:20:01 起 opencode-go 首次报错
- 15:21:58 起 deepseek 首次报错(Unsupported custom tool: exec)
- 15:44:02 100hub 503
- 16:26 前后 枣树 array_above_max_length
- 16:47 起新开 xd 通道会话全部正常
## 诊断
- 本地设置与服务商注册均完好(provider-order-prefs.json、custom_providers 表、key 文件均在)
- 错误来自上游网关拒绝请求,非本地客户端拦截
- 疑似 0.1.45 调整了发给第三方网关的工具清单(包含 exec / web_search 等),第三方网关不识别直接拒绝
- 官方 xd 通道不经过第三方网关,因此不受影响
## 建议
- 请将第三方网关(opencode.ai / api.deepseek.com / litellm 桥接)的工具白名单与客户端工具清单对齐
- 或对不支持的网关在本地降级为仅 apply_patch + 文本回复,避免上游 400 错误直接抛给用户
- 应急方案:用户可切换官方 xd 通道继续使用
Contributor guide
Research direction
Start by reproducing the 0.1.45-hotfix failures with the affected providers, then compare the request tool payload with the provider and litellm bridge capabilities. The report names provider-order-prefs.json, the custom_providers table, and key files as configuration checks. Done means unsupported tools no longer cause third-party requests to fail, while the official xd channel remains unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100