What this error means
LiteLLM forces tool_choice parameter on adaptive-thinking Anthropic models (Claude Opus 4.7 etc.) causing request rejection — fix applied in pull #28114 is a LiteLLM failure pattern reported for developers trying to fix litellm proxy errors when calling anthropic adaptive-thinking models, where litellm incorrectly forces tool_choice parameter and causes api requests to be rejected by anthropic.. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Source: BerriAI/litellm#28114 (updated 2026-05-17). Live PR fixing LiteLLM forcing unsupported tool_choice on adaptive-thinking Anthropic models. Directly impacts paid LiteLLM proxy users — every affected request wastes tokens. This was recently fixed but developers encountering it before the fix need troubleshooting guidance. Category: LiteLLM per exact mapping.
Common causes
- Source: BerriAI/litellm#28114 (updated 2026-05-17). Live PR fixing LiteLLM forcing unsupported tool_choice on adaptive-thinking Anthropic models. Directly impacts paid LiteLLM proxy users — every affected request wastes tokens. This was recently fixed but developers encountering it before the fix need troubleshooting guidance. Category: LiteLLM per exact mapping.
Quick fixes
- Confirm the exact error signature matches
LiteLLM forces tool_choice parameter on adaptive-thinking Anthropic models (Claude Opus 4.7 etc.) causing request rejection — fix applied in pull #28114. - Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
- Verify the model name, local service connectivity, and network access before retrying the model pull.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.