You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] Error from provider (Console Go): Upstream request failed — Kimi K3 #37815
I have this error for one of 3 Kimi K3 sessions, started in the middle of the work at 39% context. And reverting just the last turn resolved it. I wish I could see the details of the error message somewhere in opencode.
The Kimi K3 requests did not include OpenCode-specific mcp or top-level system fields. Changing the Go API key also did not resolve it. This points to a stale or incorrect model-specific Kimi K3 rate-limit bucket/routing state on Console Go. The generic Upstream request failed message appears alongside or after the K3-specific 429 responses.
It seems to be an issue with content review on the OpenCode proxy. I’ve found that this error occurs whenever a request mentions Chinese leaders or contains political language. On my end, this only happens with Kimi models provided through OpenCode Go.
For me it was an issue because of the long tool name in one of my MCPs. The Responses API used by Muse Spark enforces name ≤ 64 chars. One of my MCP tool name is exactly 65 char. So i disabled it and it worked.
i have same issues with that. i using model Muse Spark 1.3. i think the error because of overlimit session opencode. because when i try to restart the session, it work again
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.
Activity
github-actions commentedon Jul 19, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is already tracked in one of these, please add any additional context there rather than keeping a separate report.
ctml91 commentedon Jul 21, 2026
Any solutions for this yet?
Caffeine19 commentedon Jul 21, 2026
Same here in the VSCode Copilot.
gschadow commentedon Jul 22, 2026
I have this error for one of 3 Kimi K3 sessions, started in the middle of the work at 39% context. And reverting just the last turn resolved it. I wish I could see the details of the error message somewhere in opencode.
iamvaleriofantozzi commentedon Jul 27, 2026
I can reproduce this with a newly reset OpenCode Go plan, so this does not appear to be exhausted account quota or a client temperature override.
I tested the Go endpoint directly using the same API key and a minimal payload:
kimi-k3,temperatureomitted: HTTP 429 —Provider rate limit exceededkimi-k3,temperature: 1: HTTP 429 —Provider rate limit exceededkimi-k2.7-code,temperatureomitted: HTTP 200mimo-v2.5,temperatureomitted: HTTP 200The Kimi K3 requests did not include OpenCode-specific
mcpor top-levelsystemfields. Changing the Go API key also did not resolve it. This points to a stale or incorrect model-specific Kimi K3 rate-limit bucket/routing state on Console Go. The genericUpstream request failedmessage appears alongside or after the K3-specific 429 responses.waynezhao12 commentedon Jul 29, 2026
It seems to be an issue with content review on the OpenCode proxy. I’ve found that this error occurs whenever a request mentions Chinese leaders or contains political language. On my end, this only happens with Kimi models provided through OpenCode Go.
anon192784 commentedon Aug 24, 2026
Going to commands (ctrl+p) and changing a model to Mimo V2.5 Free worked for me (at least for now)
danielpetrica commentedon Aug 28, 2026
i have this issue with deepseek models too but not politica mention at all
stantaneous commentedon Sep 12, 2026
facing similar issue with muse spark 1.3 with opencode go subscription.
CasperOng commentedon Sep 13, 2026
Same issue with Luna
stantaneous commentedon Sep 13, 2026
For me it was an issue because of the long tool name in one of my MCPs. The Responses API used by Muse Spark enforces name ≤ 64 chars. One of my MCP tool name is exactly 65 char. So i disabled it and it worked.
kokoy13 commentedon Sep 15, 2026
i have same issues with that. i using model Muse Spark 1.3. i think the error because of overlimit session opencode. because when i try to restart the session, it work again
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊