feat: add Tavily as parallel search engine option#33
Open
tavily-integrations wants to merge 2 commits into
Open
feat: add Tavily as parallel search engine option#33tavily-integrations wants to merge 2 commits into
tavily-integrations wants to merge 2 commits into
Conversation
added 2 commits
June 16, 2026 14:04
|
Someone is attempting to deploy a commit to the Baeksang's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Tavily as a third configurable
--engine tavilysearch provider alongside the existing DuckDuckGo (default) and SearXNG options. This is an additive change — no existing providers are modified.When
--engine tavilyis used, search results feed through the sameStealthRetrieverpipeline, so full-page stealth fetch, Evidence Records, and Bot Wall detection work identically to the SearXNG path.Changes
pyproject.tomltavily-python>=0.5under a new[tavily]optional extrasrc/deepcloak/config.py'tavily'to_VALID_ENGINEsettavily_api_key: str | Nonefield toSettingsdataclassresolve()now readsTAVILY_API_KEYfrom the environmentsrc/deepcloak/retriever.pytavily_search(api_key, query, max_results)usingTavilyClient.search()build_stealth_retriever()to accept an optionalsearch_fncallable (defaults tosearxng_searchfor backward compatibility)src/deepcloak/research_core.pytavilybranch in_run_ldr()that builds theStealthRetrieverwithtavily_searchbound to the API key, gated onsettings.tavily_api_keysrc/deepcloak/cli.py'tavily'to--enginechoicesDependency changes
tavily-python>=0.5as optional extra[tavily]in pyproject.tomlEnvironment variable changes
TAVILY_API_KEY— read byconfig.resolve(); required when--engine tavilyis usedNotes for reviewers
build_stealth_retriever()signature change is backward-compatible:searxng_urlis now optional (with defaultNone) and existing callers passing it as a keyword arg continue to work unchanged.tavily-pythonis opt-in viapip install deepcloak[tavily]— it is not added to core dependencies.Automated Review
except Exception: passin research_core.py silently swallows ImportError if tavily-python is not installed, falling back to duckduckgo without user feedback — but this is consistent with the existing SearXNG branch and is not a blocker.