anomalyco / anomalyco/opencode

zen/go: mimo-v2.5 tool calls return 400 (Provider returned error)

Open
#43,481 1 comment 0 reactions 1 assignee View on GitHub

@MrMushrooooom is already working on this.

Since Aug 19, 2026.

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

Description

Problem

mimo-v2.5 on the zen/go endpoint fails when the request includes tools. Any request with a tools array → 400:

{"error":{"type":"server_error","message":"Error from provider (Console Go): Upstream request failed: [400] Provider returned error"}}

Without tools, the same request succeeds.

Repro

POST https://opencode.ai/zen/go/v1/messages with x-api-key:

{
  "model": "mimo-v2.5",
  "max_tokens": 1024,
  "messages": [{"role": "user", "content": [{"type": "text", "text": "hi"}]}],
  "tools": [{
    "name": "bash",
    "description": "Run a shell command",
    "input_schema": {"type": "object", "properties": {"cmd": {"type": "string"}}, "required": ["cmd"]}
  }]
}

→ 400. Remove tools → 200.

Confirmed independent of streaming, thinking, system prompt, and message shape (string or array content). The failure is triggered solely by the presence of tools.

Notes

  • models.dev lists tool_call = true for opencode-go/mimo-v2.5, so this looks like an upstream Console Go deployment issue, not a model limitation.
  • Other zen/go models (deepseek-v4-flash, etc.) handle tools fine on the same endpoint.
  • This makes mimo-v2.5 unusable as an agent model (Hermes / Claude Code / any tool-using client).

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.