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
Omit textVerbosity option for providers other than Azure (gpt-5) #2387
Azure's OpenAI compatible API does not seem to support that textVerbosity parameter. Currently the only way to disable sending that parameter it is to extend the azure provider. (See the code above.) I'm—however—using a proxy that uses Azure among other hosts (LiteLLM based) and have my provider configured like:
importtype{Plugin}from"@opencode-ai/plugin"exportconstRemoveUnsupportedParams: Plugin=async()=>{return{async"chat.params"({ provider, model },output){if(provider.info.id.includes("my-custom-provider")&&model.id.includes("gpt-5")){output.options["textVerbosity"]=undefined}}}}
Same issue here - when using LiteLLM proxy with GPT-5, I hit this same issue. It should be fixed properly in Opencode rather than hacking custom plugin.
@fpytloun that sounds fine then we can add an additional exclusion, can you share your opencode.json and I will figure out how we can fix it for everyone...
If the provider isn't deterministic maybe we just have a configuration option that allows you to drop a field
Activity
rekram1-node commentedon Sep 3, 2025
you may be able to use plugin here
rekram1-node commentedon Sep 3, 2025
https://github.com/sst/opencode/blob/dev/packages/plugin/src/example.ts
I think you could use this as reference and then just delete textVerbosity from the options record
I havent looked super deep but that may work
jessevdp commentedon Sep 3, 2025
Yeah that works! I ended up doing something like:
rekram1-node commentedon Sep 3, 2025
@jessevdp I think given your pretty unique usecase a plugin is suitable solution here and we should be able to close, what do you think
jessevdp commentedon Sep 3, 2025
Yeah my situation is probably pretty unique. Hopefully anyone in the same situation is able to find this thread.
mfreiwald commentedon Sep 4, 2025
Thanks for the hint with the plugin.
Just hoping that azure will fix this because everyone with this setup will have the issue..
eisterman commentedon Sep 10, 2025
There is an identical error when using LiteLLM as proxy for GPT-5, probably for an error from their side. Thank you very much for the plugin idea!
fpytloun commentedon Oct 3, 2025
Same issue here - when using LiteLLM proxy with GPT-5, I hit this same issue. It should be fixed properly in Opencode rather than hacking custom plugin.
rekram1-node commentedon Oct 3, 2025
@fpytloun that sounds fine then we can add an additional exclusion, can you share your opencode.json and I will figure out how we can fix it for everyone...
If the provider isn't deterministic maybe we just have a configuration option that allows you to drop a field
fpytloun commentedon Oct 3, 2025
@rekram1-node here's my config using LiteLLM gateway:
rekram1-node commentedon Oct 3, 2025
ig we could probably just do an additional exclusion if the provider is "litellm"
if you provider is named something else you could set this:
rekram1-node commentedon Oct 3, 2025
Idk much about litellm does it always go through that azure endpoint?
mfreiwald commentedon Oct 3, 2025
The problem is that azure doesn't support this parameter.
Checking the provider doesn't make sense in my opinion because LiteLLM provider has a different name in the config.
The model config should have something like "omitParameter" so we are more flexible regarding this.
mfreiwald commentedon Oct 3, 2025
Wait does this already work?
rekram1-node commentedon Oct 3, 2025
@mfreiwald I mean it will definitely set it to null, idk what azure will do if they process it tho
fpytloun commentedon Oct 3, 2025
There is also drop_params parameter in LiteLLM which might simply drop this parameter if unsupported by provider:
https://docs.litellm.ai/docs/completion/drop_params
thdxr commentedon Mar 25, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.