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

[zqiu8414-collab]

Description

I have a Go subscription.

Environment:

• SillyTavern (OpenAI compatible)
• Base URL: https://opencode.ai/zen/go/v1
• API key is valid.
• Models list can be fetched successfully.

Issue:

• kimi-k3: fails
• mimo-v2.5: fails
• minimax-m3: works

The request is extremely simple:

messages:

• role: user
  content: "Hi"

Backend log:

Error from provider (Console Go): Upstream request failed

I have already verified:

• Different API keys (same result on my side)
• Different SillyTavern instances (server + Android local)
• Empty chat
• No extra parameters
• Presence/Frequency penalty = 0

Interestingly:
A friend can use my API key with kimi-k3 successfully from another environment.

So the key is valid, but requests from my environment consistently fail for kimi-k3 and mimo-v2.5.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-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.

[zqiu8414-collab]

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.

[kai-kleinbard-tyto]

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).