Unknown parameter: 'reasoningSummary' with GPT-5 on Azure

[micheljung]

Description

Can't prompt anymore since v1.14.51. Worked with v1.14.50.

Unknown parameter: 'reasoningSummary'.

Plugins

OpenCode version

v1.15.0

Steps to reproduce

1. Use it with GPT-5.1 on Azure
2. Prompt anything

Probably related to #22350, #22351, #21237

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

Windows Terminal

[rekram1-node]

Are u using responses api or completions api? And u said it's w/ gpt-5.1? Not gpt-5.5?

[micheljung]

Hi @rekram1-node , thanks for checking back.

I assume the responses API? My opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "my-gpt": {
      "name": "MyGPT",
      "npm": "@ai-sdk/openai-compatible",
      "options": {
        "baseURL": "http://my-corporate-proxy/openai/deployments/gpt-5.1/"
      },
      "models": {
        "gpt-5.1": {
          "name": "GPT-5.1"
        }
      }
    }
  }
}

Then I just start opencode, type something, press enter.

[rekram1-node]

ur using the completions api since it is openai compatible pkg, ill take a look

[bertrandgressier]

I have same issue, I'm waiting a patch for this issue, all gpt5 model is not working on azure

[dylanwe]

I also have this issue when working with GPT 5 Azure models

[dylanwe]

@bertrandgressier this PR broke it #26819 and rekram1-node also has a recent comment in there with a small update #26819 (comment).

[rekram1-node]

u can always mitigate these things by overriding fetch implementations via plugins but ill fix this tmr

is everyone using azure directly or are these custom providers? Or is this litellm

extra context helps so ic an fix it for all of u

[ar27111994]

@rekram1-node I've encountered this on both Azure directly & on a custom provider. Not sure about LiteLLM, as I believe it had a security breach some time ago, so I haven't tried setting it up after that.

[ovstetun]

I have this issue using litellm - so a fix would be great :)

[AlexHird]

Have the same issue using Azure Foundry

[rekram1-node]

cool ty