anomalyco / anomalyco/opencode

[Bug] OpenCode Go: kimi-k3 无法连接(AI_APICallError: Internal server error / Upstream request failed)

Open
#41,035 2 comments 0 reactions 1 assignee View on GitHub

@fwang is already working on this.

Since Aug 7, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

opencode-go/kimi-k3 无法正常连接。选择 Kimi K3 后发起请求即失败,其它 opencode-go 模型(如 deepseek-v4-flash)正常。

现象
  • 在模型选择器中 kimi-k3 可见,但调用时报错:
    • AI_APICallError: Internal server error
    • Upstream request failed
  • 换用其它 opencode-go 模型则正常,说明非本地配置/密钥问题。
Environment
  • OpenCode 版本:CLI/Desktop 最新
  • Provider: opencode-go
  • Model: opencode-go/kimi-k3
  • OS: Windows
Steps to reproduce
  1. /connect 选择 OpenCode Go 并配置 API key。
  2. /models 选择 opencode-go/kimi-k3
  3. 发送任意 prompt。
  4. 请求失败,日志显示 providerID=opencode-go modelID=kimi-k3 -> AI_APICallError: Internal server error
Expected behavior

Kimi K3 应能正常响应,与其它 opencode-go 模型一致。

Actual behavior

调用反复失败,Internal server error

Related issues

与以下已存在 issue 高度相关(同模型、同服务、不同表现):

  • #40006 opencode-go 套餐使用异常(kimi-k3 / deepseek-v4-flash 均 Internal server error,Windows Desktop)
  • #38378 kimi-k3 在 /v1/messages 失败而 /v1/chat/completions 正常
  • #40325 Kimi K3 经 Responses API 返回空响应(缺失 output_item 事件)

疑似 Go 网关对 kimi-k3 的上游转发存在不兼容,希望团队排查 kimi-k3 的路由/翻译层。

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.