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]: OpenCode Go intermittently returns "Upstream request failed" for Kimi K2.7 Code #39250
OpenCode Go intermittently fails when calling opencodego/kimi-k2.7-code with:
Error from provider (Console Go): Upstream request failed
The same OpenCode Go account can call opencodego/glm-5.2 and opencodego/minimax-m3 successfully. A later retry of the identical Kimi request succeeded, so this appears to be an intermittent Kimi K2.7 upstream/routing reliability problem rather than an invalid model ID or authentication failure.
Plugins
oh-my-openagent / OMO The failure also occurred in a fresh session with a minimal prompt. The configured primary agent was still loaded because build was treated as a subagent and OpenCode fell back to the default agent.
OpenCode version
1.18.4
Steps to reproduce
Ensure OpenCode Go is connected and opencodego/kimi-k2.7-code appears in opencode models opencodego.
Run in PowerShell:
opencode --print-logs --log-level DEBUG run -m opencodego/kimi-k2.7-code "Reply only: OK"
Observe the intermittent error:
AI_APICallError: Error from provider (Console Go): Upstream request failed
Run comparable tests with:
opencode run -m opencodego/glm-5.2"Reply only: OK"
opencode run -m opencodego/minimax-m3 "Reply only: OK"
Both comparison models return OK. Retrying the Kimi K2.7 command may later succeed without any local configuration change.
Screenshot and/or share link
The relevant failure occurred around 2026-07-
28 03:06 UTC.
Operating System
Windows 11
Terminal
PowerShell 7.6.3
Reacted by Eugene M, Fernando Oviedo and Roman Havrylko
Activity
github-actions commentedon Jul 28, 2026
This issue might be a duplicate of existing issues. Please check:
mcp/system) being rejected by strict upstream validatorsIf your issue is the same underlying problem, consider adding a reaction or comment to one of the existing issues rather than opening a new one.
github-actions commentedon Sep 27, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.