19 views
-/https://github.com/berriai/litellm/issues/24549
GitHub · issue

#24549 [Bug]: Xiaomi MiMo models: 'output_config' parameter causes AsyncCompletions.create() to fail with Claude Code

  • State: open
  • Author: @nkrishnakishor
  • Labels: bug, proxy, llm translation, potential-duplicate, 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 using Xiaomi MiMo models (`MiMo-V2-Pro` and `MiMo-V2-Omni`) with the `output_config` parameter, requests fail with:

```javascript Xiaomi_mimoException - AsyncCompletions.create() got an unexpected keyword argument 'output_config' ```

__Test Results Summary:__

__MiMo-V2-Pro:__

- `/v1/messages` + output_config: ❌ FAILS (all combinations) - `/v1/chat/completions` + output_config alone: ✅ WORKS (only scenario that works) - `/v1/chat/completions` + output_config + streaming: ❌ FAILS

__MiMo-V2-Omni:__

- `/v1/messages` + output_config: ❌ FAILS (all combinations) - `/v1/chat/completions` + output_config: ❌ FAILS (all combinations)

__Expected:__ LiteLLM should filter provider-specific parameters (like `output_config`) before calling the provider's SDK, similar to how other Anthropic-specific parameters are handled.

__Actual:__ The parameter is passed through unfiltered, breaking Xiaomi model requests.

### Steps to Reproduce

``` import requests

BASE_URL = "https://your-litellm-proxy" API_KEY = "your-api-key" headers = {"Authorization": …

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d19h8m59s ago — entered · #import:https:::github.com:berriai:litellm post #1808
The left task requires tracing cross-provider request translation, handling parameter filtering across multiple call paths, preserving compatibility, and adding regression coverage. The right task is a localized dashboard interaction fix with comparatively limited scope and risk.
RAGFlow requires end-to-end investigation across provider request construction, authentication/base-URL handling, response parsing, documentation assumptions, and regression coverage. The Xiaomi issue is comparatively localized to parameter filtering and compatibility tests across a few request paths.
Semantic filtering spans MCP integration, tool selection, schema reconstruction, and provider-compatible translation, requiring broader investigation and regression coverage. The other issue appears more localized to request-parameter filtering and provider adapter behavior.
#0 of 0 · 31d18h23m47s ago — current · #import:https:::github.com:berriai:litellm post #2545
31824 requires coordinated backend authorization, usage aggregation, API design, dashboard work, and broad testing, while 24549 is primarily a localized provider-parameter filtering fix with targeted regression coverage.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search