ERROR: Cannot read "X" (this model does not support image input). Inform the user.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by reading ~/.config/opencode/plugins/llama-discover.ts and the Llama.cpp /models response shape described in the issue. Trace how model capabilities are registered and compare the data[] entries with architecture.input_modalities. Reproduce with a vision capable model served by Llama.cpp; done means image input is recognized instead of triggering the text-only error.
Written by the indexing model from the issue text.
Description
Description
The model is not accepting image input, despite being vision capable.
Root cause: ~/.config/opencode/plugins/llama-discover.ts iterates llama.cpp's /models data[] array but checked entry.capabilities for "multimodal". That field only exists in the parallel models[] array — data[] entries never have it.
So the check is always false, and the model is always registered text-only. The correct field on data[] entries is architecture.input_modalities, which reports ["text","image","video"] on my server.
Plugins
No response
OpenCode version
v2.0.27
Steps to reproduce
1: Load up a model like unsloth/Qwen3.8-27B-GGUF that has image support.
2: Serve it with Llama.cpp.
3: Paste an image into the prompt
4: Watch the model parrot: "ERROR: Cannot read "X" (this model does not support image input). Inform the user." default from model-request.ts because it only reads the models registered capabilities.
Screenshot and/or share link
No response
Operating System
CachyOS x86_64.
Terminal
Alacritty, Gnome, any old fish terminal.
- Dominant language
- TypeScript
- Stars
- 213k
- Forks
- 28.4k
- Avg merge
- 8h 51m
- Merged PRs (30d)
- 289
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anomalyco/opencode
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
anomalyco/opencode#55369 · 1 comment ·
Maintainers usually reply within 1 day
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
anomalyco/opencode#55351 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
anomalyco/opencode#55285 · 2 comments ·
Maintainers usually reply within 1 day
-
opencode on clean macos zsh .export path not working because it append and it fails because no ~/.zshrc filePossibly taken @fihaaade claimed this 1 day ago. Openreproduced
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anomalyco/opencode#55068 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anomalyco/opencode#54919 · 1 comment ·
Maintainers usually reply within 1 day
All issues in anomalyco/opencode
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
wormhole-foundation/wormhole#5062 ·
Maintainers usually reply within 1 day
-
internal os specific
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
frostney/GocciaScript#1688 ·
Maintainers usually reply within 1 day
-
integration:hermes
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vectorize-io/hindsight#5592 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vercel/streamdown#673 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
apache/rocketmq-dashboard#6712 ·
Maintainers usually reply within 3 days