anomalyco / anomalyco/opencode

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

Open
#39,250 1 comment 3 reactions 1 assignee View on GitHub

@StarpTech is already working on this.

Since Jul 28, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

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"
  1. Observe the intermittent error:
AI_APICallError: Error from provider (Console Go): Upstream request failed
  1. Run comparable tests with:
opencode run -m opencodego/glm-5.2 "Reply only: OK"
opencode run -m opencodego/minimax-m3 "Reply only: OK"
  1. 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-

Image

28 03:06 UTC.

Operating System

Windows 11

Terminal

PowerShell 7.6.3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.