Repository navigation
models: deepseek-v4.1-flash-free rejects image input though advertised as image-capable #61842
Description
Summary
Sending an image to opencode/deepseek-v4.1-flash-free fails with [invalid_request_error] image input is not available on this engine, even though the model is advertised as image-capable. The same model accepted screenshots until 2026-10-31, so this looks like a gateway/engine regression.
Environment
- opencode version: 2.2.5
- OS: Windows 10.0.26200 (win32 x64)
- Terminal: Unavailable:
TERM_PROGRAMnot set (TERM=xterm-256color) - Shell:
C:\Windows\system32\cmd.exe - Install/channel: desktop app bundle (
ai.opencode.desktop/resources/opencode-cli.exe), latest - Active plugins:
[email protected],opencode-dcp,@dietrichgebert/ponytail
Reproduction
-
Create a small PNG (426 bytes, red background with a blue circle).
-
Run:
opencode run -m opencode/deepseek-v4.1-flash-free -f imgtest.png "What shapes and colors are in this image? One short line." -
Optionally repeat with
-m "opencode/deepseek-v4.1-flash-free#max".
Expected Behavior
The model describes the image. models.dev lists opencode/deepseek-v4.1-flash-free as modalities.input: ["text","image"], attachment: true, so image input should be accepted.
Actual Behavior
Error: Upstream request failed: [invalid_request_error] image input is not available on this engine
(request_id: gw-ae0e2e66bcf8-192db7)
Exit code 1, no reply. Same for the #max variant (request_id: gw-add10c6ab910-192efe).
Deterministic: two fresh CLI runs plus six interactive attempts on 2026-11-04 between 23:25 and 23:30 UTC, all rejected. Engine IDs observed: gw-addc59e92621d, gw-addc3cc2c204, gw-adba25bd59c1, gw-ae0e2e66bcf8, gw-add10c6ab910 — all text-only.
Additional Context
Control run with the same file works:
opencode run -m opencode/nemotron-3.5-super-vl-free -f imgtest.png "..."
> A blue circle on a red background.
Other models on the same account:
opencode/deepseek-v4.1-flash-vision-exp→Model unavailableopencode/deepseek-v4.1-flash(paid) →Insufficient account funds(unrelated: account balance)
Regression window from local session history (~/.local/share/opencode/opencode.db), session ses_e78708eacffdFd9QXgh11m6r6B, model deepseek-v4.1-flash-free:
- 2026-10-29 12:08, 12:54, 12:56, 15:08, 15:13, 15:16, 15:20, 15:28, 15:56, 16:08 UTC — image/png attached, assistant replied normally (some replies explicitly describe screenshot content).
- 2026-10-31 12:36, 12:37, 13:02, 13:15, 13:18, 13:20, 13:25, 13:26, 15:44, 16:06, 16:48 UTC — image/png and image/jpeg attached, normal replies ("На скриншоте видно, что Wildberries…").
- 2026-11-04 23:25 UTC — first observed
image input is not available on this engine.
No config change on my side between those dates; no updates other than routine use.
Workaround: switch to opencode/nemotron-3.5-super-vl-free for image input.
Activity
opencodejr commentedon Nov 4, 2026
Thanks for the detailed report, including the request IDs and the dates from your session history.
I think this is a duplicate of #61827. It reports the same
image input is not available on this engineerror from the gateway, at the same time (2026-11-04), on 2.2.5, with DeepSeek V4.1 Flash. A commenter there hit it onopencode/deepseek-v4.1-flash-free, the same model you used. The error comes from the gateway or upstream engine, not from the OpenCode client.Possible duplicates and related issues, ordered by likelihood:
opencode/deepseek-v4.1-flash-free); appears to be the gateway sending image requests to text-only enginesYour details would help on #61827: it fails every time with a plain
-fattachment, images worked on 2026-10-31, and you have thegw-…request IDs. Please consider adding them there. Until it's resolved,opencode/nemotron-3.5-super-vl-freeworks for image input, as you found.The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
aitools1 commentedon Nov 4, 2026
Agreed, this is a duplicate of #61827 — no objection to closing it here.
I moved the extra data points there: #61827 (comment)
What it adds beyond what's already in #61827:
-fattachment of a 426-byte PNG in a fresh session, so no clipboard paste, no history re-send and no MCP tool result is needed to trigger it.gw-ae0e2e66bcf8,gw-add10c6ab910(plusgw-addc59e92621d,gw-addc3cc2c204,gw-adba25bd59c1from the interactive attempts) — different nodes from thegw-adac8a2c2d3done in go: deepseek-v4.1-flash image rejection bricks sessions ("image input is not available on this engine") #61827.opencodejr commentedon Nov 4, 2026
Thanks for confirming, and for adding the details to #61827. The
-frepro in a fresh session, the extragw-…engine IDs and the Nov 1–4 window should all help maintainers look into the gateway side. Please follow #61827 for updates. The bot will close this issue as a duplicate as planned.opencodejr commentedon Nov 5, 2026
Closing this as a duplicate of #61827, as agreed. Your extra details are now on #61827: the
-frepro in a fresh session, the extragw-…engine IDs and the Nov 1–4 window. Please follow that issue for updates. Thanks again for the thorough report.