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
[FEATURE]: Expand Openrouter Blacklist via Json #3452
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Openrouter shows a lot of good suggestions but it also shows a lot of models I have no intent of ever using and I would rather keep it clean and lean, only suggesting the models I actually want to use. I can add new models to opencode.json which is great but I need to look through 50+ random ones in the list before I get to them.
Only current workaround is to disable your built-in openrouter provider and then re-create it as a custom provider which feels largely unnecessary just to keep things tidy.
You have a blacklist function already in providers.ts that prevents openrouter from showing GPT-5 models. Can we expand upon this filter and make it customizable via opencode.json so we can tailor the openrouter provider to be more specific to our needs?
This issue might be a duplicate of existing issues. Please check:
[FEATURE]: Disabling specific models through opencode.json #3411: [FEATURE]: Disabling specific models through opencode.json - This issue requests the exact same functionality to disable specific models in opencode.json so they don't show up in the model list, with the same use case of OpenRouter providing many unwanted models.
Feel free to ignore if none of these address your specific case.
@KHAEntertainment what if this was possible via the opencode plugin system, where you could have strong control of what ends up being in the list and what is dropped
@KHAEntertainment what if this was possible via the opencode plugin system, where you could have strong control of what ends up being in the list and what is dropped
Would that be good?
Sure. I only suggested a method as it seemed like you already had it partially implemented but whatever means you guys want to take to make the models filterable is fine with me. Thanks for the quick response!
@KHAEntertainment yeah the think we have rn is just filtering out the gpt-5-chat models because unlike most gpt-5 variations they dont support tool calling and people kept filing bug reports even tho gpt-5-chat was behaving as expected so we decided to just "blacklist" it essentially until we could indicate it in the tui better
Activity
github-actions commentedon Oct 25, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
rekram1-node commentedon Oct 26, 2025
@KHAEntertainment what if this was possible via the opencode plugin system, where you could have strong control of what ends up being in the list and what is dropped
Would that be good?
KHAEntertainment commentedon Oct 26, 2025
Sure. I only suggested a method as it seemed like you already had it partially implemented but whatever means you guys want to take to make the models filterable is fine with me. Thanks for the quick response!
rekram1-node commentedon Oct 26, 2025
@KHAEntertainment yeah the think we have rn is just filtering out the
gpt-5-chatmodels because unlike most gpt-5 variations they dont support tool calling and people kept filing bug reports even tho gpt-5-chat was behaving as expected so we decided to just "blacklist" it essentially until we could indicate it in the tui betterNo problem!
rekram1-node commentedon Oct 27, 2025
For whatever reason I was way overcomplicating this I thought you meant something else.
Yeah a simple blacklist can just be added into the config I think there is an open pr adding it actually