[BUG]: OpenCode Go intermittently returns "Upstream request failed" for Kimi K2.7 Code

[KaysonSear]

Description

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

1. Ensure OpenCode Go is connected and opencodego/kimi-k2.7-code appears in opencode models opencodego.
2. Run in PowerShell:

opencode --print-logs --log-level DEBUG run -m opencodego/kimi-k2.7-code "Reply only: OK"

3. Observe the intermittent error:

AI_APICallError: Error from provider (Console Go): Upstream request failed

4. Run comparable tests with:

opencode run -m opencodego/glm-5.2 "Reply only: OK"
opencode run -m opencodego/minimax-m3 "Reply only: OK"

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

[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: Same "Error from provider (Console Go): Upstream request failed" error specifically with Kimi models on OpenCode Go
• 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: Covers kimi-k2.7-code specifically among multiple affected models, with a root cause analysis pointing to non-standard fields (mcp/system) being rejected by strict upstream validators
• [Bug] OpenCode Go: kimi-k3 fails on /v1/messages with "Upstream request failed" while /v1/chat/completions succeeds #38378: Kimi K3 upstream request failure on OpenCode Go with a workaround via a different endpoint

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