8 views
-/https://github.com/berriai/litellm/issues/27091
GitHub · issue

#27091 [Bug]: Claude Code + Microsoft Foundry (Azure) - Unsupported 'reasoning.effort' and AnthropicResponse Pydantic Validation Error

  • State: open
  • Author: @CyberTron957
  • Labels: bug, proxy, llm translation, claude code

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

I am using LiteLLM as an anthropic_proxy to route Claude Code requests to a model (Kimi-K2.6) hosted on Microsoft Foundry (formerly Azure AI Foundry). Two distinct issues occur:

Parameter Mapping Failure: Claude Code sends "thinking/reasoning" parameters. LiteLLM translates these to reasoning.effort (OpenAI format). Microsoft Foundry models (non-o1) reject the request with a 400 Bad Request: Unsupported parameter: 'reasoning.effort'. Even with drop_params: true, this specific parameter persists because it is a "valid" OpenAI key, despite being unsupported by the specific deployment.

Telemetry/Logging Crash (Non-Blocking): After a successful response (if params are manually dropped), LiteLLM's background logging fails. It attempts to validate a ResponseIncompleteEvent or ResponseCompletedEvent against the AnthropicResponse Pydantic model, causing a ValidationError.

### Steps to Reproduce

1. Run LiteLLM Proxy with the following config.yaml:

model_list: - model_name: Kimi-K2.6 litellm_params: model: openai/your-deployment ap…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h49m4s ago — entered · #import:https:::github.com:berriai:litellm post #2040
Issue 27091 is harder because it spans request-translation behavior, provider-specific parameter filtering, and asynchronous response/telemetry validation, with compatibility and regression risks across multiple proxy paths. Issue 31861 is comparatively localized to a performance-sensitive buffer implementation and focused tests.
#0 of 0 · 31d18h24m35s ago — current · #import:https:::github.com:berriai:litellm post #2428
The right issue spans provider-specific parameter translation, conditional dropping behavior, and asynchronous event-model validation, requiring reproduction across proxy, request transformation, and telemetry paths. The left is primarily a documentation or cookbook contribution with limited implementation risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search