Console Go: kimi-k3 and mimo-v2 fail with "Upstream request failed", minimax-m3 works #39627

Activity

1. github-actions

   assigned

   StarpTech

   on Jul 30, 2026
2. github-actions commented on Jul 30, 2026

   

   github-actionsBot

   on Jul 30, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [Bug] Error from provider (Console Go): Upstream request failed — Kimi K3 #37815: [Bug] Error from provider (Console Go): Upstream request failed — Kimi K3 (same error, same model, same provider)
   • [Bug] OpenCode Go: kimi-k3 fails on /v1/messages with "Upstream request failed" while /v1/chat/completions succeeds #38378: [Bug] OpenCode Go: kimi-k3 fails on /v1/messages with "Upstream request failed" while /v1/chat/completions succeeds (same model and error)
   • OpenCode Go: kimi-k3, kimi-k2.6, kimi-k2.7-code, glm-5.2, grok-4.5, qwen3.7-max, hy3-preview all fail with 'Upstream request failed' — non-standard 'mcp'/'system' fields rejected by strict provider validators #37771: OpenCode Go: kimi-k3 and other models fail with 'Upstream request failed' — non-standard fields rejected by strict provider validators (broader issue covering kimi-k3)

   If your issue is the same as one of these, please add a comment there instead so the discussion stays focused. If your issue is distinct (e.g. environment-specific routing or a different root cause), please clarify what makes it different.
3. zqiu8414-collab commented on Jul 30, 2026

   

   zqiu8414-collab

   on Jul 30, 2026

   Last edited by zqiu8414-collab

   Author

   More actions

   Only specific providers fail from my environment.
   Additional information:

   I found similar issues, but my case seems slightly different.

   My friend can use my API key with kimi-k3 successfully in SillyTavern.

   However, in my environment, neither my own key nor my friend's key works with kimi-k3.

   Working models:

   • minimax-m3
   • glm-5.2

   Failing models:

   • kimi-k3
   • mimo-v2

   Tested on:

   • Windows local SillyTavern
   • Android local SillyTavern
   • Cloud server SillyTavern

   This may be related to environment-specific routing or provider access.
4. zqiu8414-collab

   closed this as completedon Jul 30, 2026
5. zqiu8414-collab

   reopened this on Jul 30, 2026
6. kai-kleinbard-tyto commented on Jul 30, 2026

   

   kai-kleinbard-tyto

   on Jul 30, 2026

   More actions

   Closing — no template used, insufficient information to investigate. Please reopen with the Bug Report or Feature Request template filled out (version, OS, repro steps, logs).
7. github-actions commented on Sep 29, 2026

   

   github-actionsBot

   on Sep 29, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
8. github-actions

   closed this as not plannedon Sep 29, 2026