Bug: Unknown parameter: 'reasoningEffort'. Did you mean 'reasoning_effort'?

When using GPT-5 from azure I get the following error.

Log Output

AzureException BadRequestError - Unknown parameter: 'reasoningEffort'. Did you mean
'reasoning_effort'?. Received Model Group=gpt-5
Available Model Group Fallbacks=None

+1

I'm not sure if this is the same but with gpt5 I get this error:

AI_APICallError: Unsupported parameter: 'reasoning.effort' is not supported with this model.

@thdxr

I see this was marked as closed but I'm still seeing the issue in v0.4.18


AI_APICallError: AzureException BadRequestError - Unknown parameter: 'reasoningEffort'. Did you mean
'reasoning_effort'?. Received Model Group=gpt-5
Available Model Group Fallbacks=None

@thdxr was this fixed in a different version then this ?

I can't use GPT-5
Cleaning .cache/opencode doesn't help
AI_APICallError: Unsupported parameter: 'reasoning.effort' is not supported with this model.

I just ran into this issue too:

AzureException BadRequestError - Unknown parameter: 'reasoningEffort'

I did attempt to rm -rf ~/.cache/opencode without luck.

I'm on version:

$ opencode -v
0.5.29

Does anyone know what's going on?

seems like this issue wasn’t quite fixed, I will reopen and investigate it

I've traced the issue here:

vercel/ai#8372

The client is sending both the camel cased and snake cased version.

fwiw I'm on the latest and no longer have this issue. I didn't do anything special other than let the software update

My PR for @ai-sdk/openai-compatible has been merged: vercel/ai#8392. Should be released later today.

sweet

Sorta related though, since the code is pretty much co-located:

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 it is to extend the azure provider. 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": {}
    }
  }
}

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

Should I open a separate issue? (probably right..)

@jessevdp

Should I open a separate issue? (probably right..)

yes plz! @jessevdp

@rekram1-node

done! #2387 @rekram1-node

The fix to @ai-sdk/openai-compatible was released: https://github.com/vercel/ai/releases/tag/%40ai-sdk%2Fopenai-compatible%401.0.14. I can confirm that after forcing an install of the latest version (by running rm -rf ~/.cache/opencode ) that only reasoning_effort is sent and not reasoningEffort, fixing this issue.

OK to close this one?

yeah I think we can close now

fix(app): prevent stale Den org refreshes (anomalyco#1742)

Navigation Menu

Repository navigation

Bug: Unknown parameter: 'reasoningEffort'. Did you mean 'reasoning_effort'? #1742

Log Output

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Bug: Unknown parameter: 'reasoningEffort'. Did you mean 'reasoning_effort'? #1742

Description

Log Output

Activity

otomist commented on Aug 9, 2025

bcardarella commented on Aug 11, 2025

ncecere commented on Aug 11, 2025

Salmin commented on Aug 12, 2025

jessevdp commented on Sep 1, 2025

rekram1-node commented on Sep 1, 2025

jessevdp commented on Sep 1, 2025

bcardarella commented on Sep 1, 2025

jessevdp commented on Sep 2, 2025

rekram1-node commented on Sep 2, 2025

jessevdp commented on Sep 2, 2025

rekram1-node commented on Sep 2, 2025

jessevdp commented on Sep 3, 2025

jessevdp commented on Sep 3, 2025

rekram1-node commented on Sep 3, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions