Repository navigation
schema rejects valid custom provider model in top-level model field #46248
Description
Description
The schema https://opencode.ai/config.json depends on a giant enum from models.dev
"model": {
"type": "string",
"description": "Model to use in the format of provider/model, eg anthropic/claude-2",
"$ref": "https://models.dev/model-schema.json#/$defs/Model"
}When creating a custom provider, this results in a schema validation error. Example minimal opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"provider": {
"internal": {
"npm": "@ai-sdk/openai-compatible",
"models": {
"Qwen/Qwen3-Coder-30B-A3B-Instruct": {}
}
}
},
"model": "internal/Qwen/Qwen3-Coder-30B-A3B-Instruct"
}Custom providers should be valid.
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Aug 30, 2026
This issue might be a duplicate of or closely related to an existing issue. Please check:
opencode.ai/config.jsonrejects valid V2 fields more broadly — themodelfield's$refto the models.dev enum is one specific manifestation of the same underlying schema drift problem.cash commentedon Aug 30, 2026
This was tested with VSCode's schema validator and is more specific than the general issue of #43748 and it is not clear that fixing that issue fixes this one.