Repository navigation
opencode-go: mimo-v2.6-flash vision reads a stale image after ≥5 images in one session #50823
Description
Description
Via OpenCode Go, mimo-v2.6-flash (and mimo-v2.6-pro) stops reading the newest image once 5+ images are in a single conversation: it answers with an earlier image's content, HTTP 200, no error. It reproduces with a standalone script (no OpenCode client involved) and also on OpenRouter with the same model, so it looks upstream/model-side — opening here because the model is consumed through opencode-go. A known-issues note or a cap/warning would prevent silently wrong results for users.
Steps to reproduce
- One conversation, one image per turn (large black letter on white), ask: "The new attached image shows exactly one large black capital letter on white. Reply with that single letter only."
- Sequence
A,E,F,H,K,L,T,X→ expectedA,E,F,H,K,L,T,X, gotA,E,F,H,H,H,T,T(3/3 runs, deterministic). 4 images PASS; 5th image already misread. node repro.mjs --provider opencode-go(self-contained script; link below)
Screenshot and/or share link
Gist with reproducer + raw per-turn evidence: https://gist.github.com/debikurnia/6b549269f79f3e02f46b6fe830e79e58. Verbatim model reasoning at the first bad turn (expected K, answered H): "…the latest attached image… The image displays a black capital letter "H"…".
Operating System
macOS (n/a — this is an API/model-level issue, no OpenCode client involved)
Terminal
n/a
Additional context
- Controls through the same gateway: fresh session per turn PASS, text-only history PASS,
mimo-v2.5PASS,kimi-k3PASS,mimo-v2.6-proFAIL. - Cross-gateway: same failure on OpenRouter → likely model-side, not opencode-go specific.
- Upstream report: [BUG] MiMo-V2.6-Flash/Pro: vision reads a stale image once ≥5 images are in one conversation XiaomiMiMo/MiMo-Code#2508
Activity
sogeisetsu commentedon Oct 15, 2026
Worse than just stale now: every image on
mimo-v2.6-flashis rejected outright, not only misread from the 5th on.POST https://opencode.ai/zen/go/v1/chat/completions,mimo-v2.6-flash, text + one 1x1 PNG (freshx-opencode-session) → HTTP 400Upstream request failed: [400] Invalid request parameters. Text-only to the same model → 200. The identical body withdeepseek-v4.1-flashorglm-5.3-flash→ 200 and the model describes the image. Same 400 onmimo-v2.6-proandmimo-v2.5. In the client it surfaces asUpstream request failed: [unsupported_media] This model reads text only; remove images and video from the messages.Details, with the raw body and the model-by-model table: #55785. That report has the same endpoint-only repro, no client involved. So image input for these models looks disabled on the serving side at some point after this issue was filed, and the stale-image behaviour described here may no longer be reachable.
sogeisetsu commentedon Oct 17, 2026
Update: the outright rejection of every image I hit on 2026-10-15 is gone. On 2026-10-17
mimo-v2.6-flashaccepts an image and answers about it (plain curl, 200; same onmimo-v2.6-pro). I have not retested the >=5-images stale-read case, so that part of this issue is still open.neriousy commentedon Oct 20, 2026
Thanks for the detailed reproduction. Your standalone script reproduces the stale-image behavior with MiMo V2.6 Flash through both OpenCode Go and OpenRouter, without the OpenCode client. I'm closing this as an upstream model issue. Please follow XiaomiMiMo/MiMo-Code#2508 for updates.