Omit textVerbosity option for providers other than Azure (gpt-5)

[jessevdp]

https://github.com/sst/opencode/blob/d6350a7fa61702ac2aa74357e901d59f2c4ee1c7/packages/opencode/src/provider/transform.ts#L94-L97

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:

{
  "provider": {
    "my-custom-provider": {
      "name": "My Custom Provider",
      "npm": "@ai-sdk/openai-compatible",
      "options": {
        "baseURL": "https://my-provider.com",
        "apiKey": "...",
        "includeUsage": true
      },
      "models": {
        "gpt-5": {}
      }
    }
  }
}

And see errors like:

AzureException BadRequestError - Unknown parameter: 'textVerbosity'

Any ideas on how we could hint at the config that the backend doesn't support that option?

[rekram1-node]

you may be able to use plugin here

[rekram1-node]

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]

Yeah that works! I ended up doing something like:

import type { Plugin } from "@opencode-ai/plugin"

export const RemoveUnsupportedParams: 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
      }
    }
  }
}

[rekram1-node]

@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]

Yeah my situation is probably pretty unique. Hopefully anyone in the same situation is able to find this thread.

[mfreiwald]

Thanks for the hint with the plugin.
Just hoping that azure will fix this because everyone with this setup will have the issue..

[eisterman]

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]

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]

@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]

@rekram1-node here's my config using LiteLLM gateway:

  "provider": {                                                                                                                       
    "litellm": {                                                                                                                      
      "npm": "@ai-sdk/openai-compatible",                                                                                             
      "name": "LiteLLM",                                                                                                              
      "options": {                                                                                                                    
        "baseURL": "https://litellm.domain.tld",                                                                                           
        "apiKey": "{env:LITELLM_OPENAI_API_KEY}"                                                                                          
      },                                                                                                                              
      "models": {                                                                                                                     
        // OpenAI                                                                                                                     
        "gpt-4.1": {},                                                                                                                
        "gpt-4.1-mini": {},                                                                                                           
        "gpt-4o": {},                                                                                                                 
        "gpt-5": {},                                                                                                                  
      }                                                                                                                               
    }                                                                                                                                 
  },

[rekram1-node]

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:

{
  "provider": {
    "your-provider": {
      "models": {
        "gpt-5": {
          "options": {
            "textVerbosity": null
          }
        }
      }
    }

}
 
}

[rekram1-node]

Idk much about litellm does it always go through that azure endpoint?