You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Non-vision models fail even when user only sends text - OpenCode auto-reads clipboard images #26668
When using a non-vision model (e.g., DeepSeek V4 Flash), users cannot send plain text messages because OpenCode automatically reads images from the clipboard and tries to send them to the model, even when the user hasn't attached any images.
Steps to Reproduce
Configure DeepSeek V4 Flash model (non-vision)
Copy an image to clipboard (screenshot, etc.)
Type a text-only message in OpenCode (no image attached)
Submit the message
Error: "Cannot read 'clipboard' (this model does not support image input)."
Expected Behavior
OpenCode should NOT automatically read clipboard images when user only sends text
Or provide a config option to disable auto clipboard image reading
Actual Behavior
Even with no image attached to the message, OpenCode reads clipboard and fails
Other models (e.g., minimax-m2.5-free) work fine because they might handle this differently
Evidence
Error message shown:
ERROR: Cannot read "clipboard" (this model does not support image input). Inform the user.
Note: The user never attached any image - it was purely a text message.
This issue might be a duplicate of existing issues. Please check:
Clipboard images routed directly to model instead of MCP when model lacks vision support #18437: Clipboard images routed directly to model instead of MCP when model lacks vision support — describes the same bug with the same error message ("Cannot read 'image' (this model does not support image input)") when a clipboard image is present but the user only sends text with a non-vision model.
If the underlying issue is still unresolved or has regressed, please mention that in a comment so maintainers can track it appropriately.
Activity
github-actions commentedon May 10, 2026
This issue might be a duplicate of existing issues. Please check:
If the underlying issue is still unresolved or has regressed, please mention that in a comment so maintainers can track it appropriately.
github-actions commentedon Jul 10, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.