Repository navigation
Model options are not forwarded for openai-compatible providers unless provider.name option is given #971
Description
Custom model options are not forwarded correctly when provider are using @ai-sdk\openai-compatible.
This can be mitigated by explicitly indicating "name" value in the provider config. E.g:
"openrouter": {
"options": {
"name": "OpenRouter" // models.options is not forwarded without this
},
"models": {
"qwen/qwen3-235b-a22b": {
"name": "Qwen3",
"tool_call": false,
"options": {
"OpenRouter": {
"provider": {
"order": [
"cerebras"
],
"allow_fallbacks": false
}
}
}
}
}
}This is due to @ai-sdk\openai-compatible searching for providerOptions based on the provideerOptionsName attribute, which is not set by opencode by default. ai-sdk code responsible for option selection.
Metadata
Metadata
Assignees
Labels
No labels
Activity
thdxr commentedon Jul 14, 2025
interesting - we i set them like this
AurelienTollard commentedon Jul 14, 2025
From what I see
openaiCompatiblefield is only used from within the prompt option definition, rather than at the model/provider levelrekram1-node commentedon Dec 28, 2025
[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Merge pull request anomalyco#971 from Lidang-Jiang/fix/codex-mcp-star…
sampling-config: gemma4:26b-ailang variant + opencode option pass-thr…
docs(skill): rig operations runbook — consolidated lessons from 2026-…
fix(local-models): one output budget per model, and stop pinning num_…