Repository navigation
provider.<id> whitelist/blacklist has no effect on the model picker (confirmed for both built-in opencode and openrouter providers) #61110
Description
Description
The whitelist (and blacklist) option under provider.<id> in opencode.json has no effect when applied to the built-in opencode zen provider (the free-tier account-linked provider). The model picker continues to show every model from the provider (including paid ones requiring a separate API key) instead of being filtered to the whitelisted set.
The same config works as documented when I tested the equivalent whitelist/blacklist syntax's schema shape (confirmed via https://opencode.ai/config.json), so this looks specific to the opencode provider, not a general config-parsing issue.
Steps to reproduce
- Log in with
opencode auth login opencode. - Add to
opencode.json:{ "provider": { "opencode": { "whitelist": ["flint-40b-free", "beam-free", "big-pickle"] } } } - Restart the background service (
opencode service restart) and reopen the TUI. - Open the model picker (
/modelsor the model selector).
Expected
Only the whitelisted models (Flint 40B Free, Beam Free, Big Pickle) appear under "Personal / OpenCode".
Actual
All models from the opencode provider still appear, both free and paid (e.g. Claude Sonnet 5.5, GPT-6 Luna, Grok 4.7, etc. all still show up unfiltered).
Environment
- opencode v2.2.5
- macOS (Apple Silicon, M2 Pro)
Activity
opencodejr commentedon Nov 1, 2026
Thanks for the clear report! I think this is a duplicate of #49986.
In v2,
whitelistandblacklistunder a provider aren't applied for any provider, not onlyopencode. They're dropped while the config is loaded, and the logs show anomitted unsupported legacy settingwarning for$.provider.opencode.whitelist. The provider docs still describe these options, which is why the config looks like it should work.Related issues, most likely first:
whitelist/blacklistare dropped in v2, with a request for a native v2 replacement (open)provider.opencode.whitelist, closed as a duplicate of [FEATURE]: Add a native V2 replacement for provider model filtering #49986whitelist/blacklistwork again by turning them into model overridesFor now, you can hide specific models one at a time:
{ "providers": { "opencode": { "models": { "<model-id>": { "disabled": true } } } } }There's also a community plugin linked in #49986 that brings back the
whitelist/blacklistfiltering.The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. Feel free to add your use case to #49986.
maksym6866 commentedon Nov 2, 2026
Confirmed this is not specific to the built-in
opencodeprovider — it also affects a standard models.dev-backed provider likeopenrouter.Steps to reproduce (openrouter)
opencode auth login openrouter.opencode.json:{ "provider": { "openrouter": { "whitelist": ["nemotron-3-ultra-550b-a55b:free", "nemotron-3.5-super-vl:free", "nemotron-3.5-lightning:free"], "models": { "nvidia/nemotron-3-ultra-550b-a55b:free": { "name": "Nemotron 3 Ultra (free)" }, "nvidia/nemotron-3.5-super-vl:free": { "name": "Nemotron 3.5 Super VL (free)" }, "nvidia/nemotron-3.5-lightning:free": { "name": "Nemotron 3.5 Lightning (free)" } } } } }opencode service restart).opencode modelsor open the model picker.Expected
Only the 3 whitelisted OpenRouter models appear.
Actual
opencode modelslists the entire OpenRouter catalog (300+ models), unfiltered — thewhitelisthas no effect. The models themselves work fine when invoked directly by ID (opencode run -m openrouter/nvidia/nemotron-3.5-lightning:free "..."responds correctly), so this is purely a model-listing/filtering bug, not an auth or routing issue.This suggests
whitelist/blacklistis broken for provider config in general, not just the account-linkedopencodeprovider. Updating the title to reflect the broader scope would help others find this.Environment
[-]provider.opencode whitelist/blacklist has no effect on the built-in opencode (zen) provider's model picker[/-][+]provider.<id> whitelist/blacklist has no effect on the model picker (confirmed for both built-in opencode and openrouter providers)[/+]opencodejr commentedon Nov 2, 2026
Closing this as a duplicate of #49986, since there hasn't been a reply saying how it's different. In v2, per-provider
whitelist/blacklistare dropped while the config is loaded, for every provider includingopencode. #49986 tracks a native v2 replacement, and #54372 is an open PR that would make these options work again.In the meantime, you can hide individual models with
providers.opencode.models.<model-id>.disabled: true, or use the community plugin linked in #49986. Please follow #49986 for updates. If your problem turns out to be different, reply here and we'll take another look.