mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-13 07:40:59 +00:00
bac968c0bf
Azure AI Foundry reasoning deployments behind an "Own server" connection reject function tools on /v1/chat/completions at their default reasoning effort and answer HTTP 400 naming reasoning_effort. The Responses API switch from #2792 only covers direct OpenAI keys, so the assistant could not run on these deployments at all. The chat client still never sends reasoning_effort, so servers that do not know the field (Ollama, LM Studio, vLLM, OpenRouter) see unchanged requests. When a request with tools is refused over reasoning_effort, it goes out once more with reasoning_effort "none", and the rest of the turn keeps sending it. The refused field is now carried on AiProviderError instead of only being logged. Fixes #3043