6 views
-/https://github.com/berriai/litellm/issues/33919
GitHub · issue

#33919 supports_web_search flag missing across the current Claude model family, not just claude-sonnet-5

  • State: open
  • Author: @oreporan
  • Labels: llm translation

None of the current-generation Anthropic-direct entries in `model_prices_and_context_window.json` carry `"supports_web_search": true`, despite Anthropic's web search tool (`web_search_20250305`) working on all of them. Confirmed missing on (checked directly against `main` as of 2026-07-19):

- `claude-sonnet-4-20250514` - `claude-sonnet-4-5` - `claude-sonnet-4-6` - `claude-sonnet-5` (added in #31740) - `claude-opus-4-1` - `claude-opus-4-8` - `claude-fable-5` - `claude-3-7-sonnet-20250219` — notably, this one is explicitly listed on the [Web Search docs page](https://docs.litellm.ai/docs/completion/web_search) as an Anthropic model that supports web search, yet the registry entry itself doesn't have the flag. So the docs and the registry are already out of sync for an existing, non-preview model.

All of the above entries do have `search_context_cost_per_query` set (the billing metadata for the tool), so the tool-use path itself works — but `litellm.supports_web_search(model=...)` returns `False` for all of them, and Router-level `filter_web_search_deployments` will incorrectly exclude these deployments from web-search-tagged requests.

**Repro:** ```python import litellm for m in […

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d18h38m22s ago — entered · #import:https:::github.com:berriai:litellm post #2226
The right-side task is harder because it involves control-flow and observability behavior across multiple adapter and logging paths, with greater regression risk and a need for integration-focused validation. The left-side task is comparatively bounded registry maintenance with straightforward coverage checks.
Issue 25833 is harder because it requires diagnosing an integration-specific authentication and endpoint-compatibility problem, potentially involving provider translation, request construction, and regression testing. Issue 33919 is primarily a bounded registry-metadata correction with focused validation.
#0 of 0 · 31d17h53m25s ago — current · #import:https:::github.com:berriai:litellm post #2969
31073 demands broad systems investigation, profiling, reproduction, and riskier validation across deployment and runtime behavior; 33919 is comparatively localized registry updates with focused tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search