Repository navigation
Provider-level model filtering (blacklist/whitelist) in config schema is silently dropped as "unsupported legacy setting" #53671
Description
Describe the bug
The published config schema (https://opencode.ai/config.json) defines blacklist and whitelist arrays on ProviderConfig, but at runtime both fields are stripped during config normalization:
level=WARN message="configuration normalization diagnostic" source=~/.config/opencode/opencode.jsonc path=$.provider.opencode.whitelist kind=unsupported action="omitted unsupported legacy setting" role=server
So there is currently no working way to filter models within a provider:
- Per-provider
whitelist/blacklistin config → silently ignored (log above), tested on 2.0.23 and 2.0.24. - Top-level
enabled_providers/disabled_providers→ provider-level only. - Defining
modelsfor a models.dev catalog provider merges with the catalog entry instead of replacing it.
Use case
The OpenCode Zen provider catalog (and several community providers) mixes free and paid models. On the free tier the picker still lists every paid model, and there is no supported way to show only *-free models (or hide specific ones). A per-provider model filter would also help any provider whose upstream serves a large mixed catalog.
Expected behavior
Either honor the schema's blacklist/whitelist per provider, or document a supported per-model hidden/enabled flag in the config.
Environment
- opencode desktop 2.0.23 / 2.0.24 (
cli serve --service), macOS 23.3.0 arm64 - config:
~/.config/opencode/opencode.jsonc
Activity
opencode-agent commentedon Oct 7, 2026
Thanks for the detailed report! This is already tracked in #49986: on v2, per-provider
whitelist/blacklistgets dropped during config normalization with the same "omitted unsupported legacy setting" warning, and there's no native v2 replacement yet. That issue asks for exactly what you describe, either a v2 per-provider model filter or clear docs on what replaces it. A comment there also links a community plugin that brings the filtering back in v2, which might help in the meantime.Please follow #49986 for updates; adding your use case there (showing only
*-freemodels on the Zen free tier) would help. The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.github-actions commentedon Oct 7, 2026
This issue might be a duplicate of an existing issue. Please check:
whitelist/blacklistbeing dropped by V2 normalization with the same “omitted unsupported legacy setting” diagnostic, and requests a native V2 replacement.opencode-agent commentedon Oct 8, 2026
Closing this as a duplicate of #49986, since there hasn't been a reply saying how it's different. That issue covers the same problem: per-provider
whitelist/blacklistis dropped as an "unsupported legacy setting" in v2, and there's no native replacement yet. Please follow #49986 for updates, and feel free to add your Zen free-tier use case there. A comment on that issue also links a community plugin that brings the filtering back in the meantime. If your problem turns out to be different, reply here and we can take another look. Thanks!