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

#26224 [Bug]: `auto_router/complexity_router` rejects `thinking.type=adaptive` for Claude Code requests

  • State: open
  • Author: @escon1004
  • Labels: bug, 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?

When sending a Claude Code / Anthropic Messages style request through LiteLLM with:

- `thinking: { "type": "adaptive" }` - `output_config: { "effort": "high" }`

LiteLLM returns:

`400 {"message":"adaptive thinking is not supported on this model"}`

This happens in two cases:

1. When the request is sent to `auto_router/complexity_router` 2. When the request is sent directly to `claude-sonnet-4-6`

The issue is unexpected because the downstream target model is `claude-sonnet-4-6`, which should support adaptive thinking.

I reduced the request payload to the minimum relevant fields below. The original request was generated by Claude Code / Anthropic Messages style clients and included tools/system content, but the failure appears tied to the `thinking.type=adaptive` handling rather than the full prompt contents.

### Steps to Reproduce

1. Configure LiteLLM with a router model using `auto_router/complexity_router`, with all tiers pointing to `claude-sonnet-4-6`.

Example router config: ```json { "model": "auto_router/complexity_router", …

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d18h50m56s ago — entered · #import:https:::github.com:berriai:litellm post #2015
Issue 32575 is harder because it spans persistence hydration, process startup lifecycle, runtime state management, API/UI consistency, and regression testing across deployment paths. Issue 26224 is more localized to request validation and provider-translation behavior with targeted compatibility tests.
#0 of 0 · 31d18h40m0s ago — current · #import:https:::github.com:berriai:litellm post #2199
The left item is substantially harder because it requires cross-cutting routing architecture, new state and configuration models, quota accounting, selection algorithms, concurrency handling, compatibility work, and broad testing. The right is comparatively localized to request handling and regression coverage.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search