fix(proxy_server): pass search_tools to Router during DB-triggered in…

[Harshit28j]

…itialization

Relevant issues

Fixes #16634 where search_tools were ignored when the Router was initialized via the database persistence path (e.g., no strict local config file).

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:
• CI run for the last commit
  Link:
• Merge / cherry-pick CI run
  Links:

Type

🐛 Bug Fix

Changes

• Refactored _update_llm_router: Moved search_tools parsing to the beginning of the function.
• Fixed Initialization: Passed the parsed search_tools to the litellm.Router constructor when creating a new router instance. This ensures search tools are available even when the router is initialized lazily from the database (e.g., llm_router is None).
• Cleanup: Removed the redundant update_router_search_tools call at the end of the function to prevent duplicate processing and log spam.
• Verification: Verified locally confirming that google-search is correctly found and executed by the Router.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
litellm	Error		Jan 20, 2026 3:26am