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
Error: "this model does not support image input" with paid providers (GitHub Copilot, Anthropic, etc.) but works with free models #16468
Still hitting this on v1.15.4 (Windows). Custom provider using @ai-sdk/openai with baseURL override — model is gpt-5.5 which is multimodal, but OpenCode reports capabilities.input.image: false.
Tried every config-level workaround I could find:
Adding vision: true to the model definition — ignored
Switching npm adapter from @ai-sdk/openai-compatible to @ai-sdk/openai — no change
Using a model ID that OpenCode recognizes (gpt-4o) under the custom provider — still false
The capability registry appears to be entirely hardcoded in the Go binary and ignores user config overrides. This makes all custom/proxy providers unable to use image input regardless of the model's actual capabilities.
Would love to see either:
A config-level capabilities override that the registry respects, or
The registry updated to include gpt-5.5 (released by OpenAI, multimodal)
Activity
github-actions commentedon Mar 7, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is distinct (e.g., specifically about the paid vs free provider distinction), please add more detail to differentiate it from the above.
mtomas7 commentedon Mar 10, 2026
Please see if this config tip will help: #15728 (comment)
botlong commentedon May 18, 2026
Still hitting this on v1.15.4 (Windows). Custom provider using
@ai-sdk/openaiwithbaseURLoverride — model isgpt-5.5which is multimodal, but OpenCode reportscapabilities.input.image: false.Tried every config-level workaround I could find:
vision: trueto the model definition — ignoredcapabilities: { input: { image: true } }— ignoredattachment: true— setscapabilities.attachment: truebutinput.imagestays false@ai-sdk/openai-compatibleto@ai-sdk/openai— no changegpt-4o) under the custom provider — still falseThe capability registry appears to be entirely hardcoded in the Go binary and ignores user config overrides. This makes all custom/proxy providers unable to use image input regardless of the model's actual capabilities.
Would love to see either:
capabilitiesoverride that the registry respects, orgpt-5.5(released by OpenAI, multimodal)Thanks for the great project otherwise!
rekram1-node commentedon May 18, 2026
There is no "go binary" if u are using a custom model u can define it like so:
valthebald commentedon Jun 25, 2026
@rekram1-node you saved my day!