🔍 feat: add Tavily as Search and Scraper Provider by yashwanth-alapati · Pull Request #12581 · LibreChat-AI/LibreChat

yashwanth-alapati · 2026-04-09T02:03:43Z

Pull Request Template

Summary

Adds Tavily as a search provider and scraper provider
Separate tavilySearchOptions and tavilyScraperOptions config blocks for full control over Tavily Search and Extract API parameters
Frontend UI updated with Tavily in provider/scraper dropdowns

Change Type

Please delete any irrelevant options.

New feature (non-breaking change which adds functionality)
This change requires a documentation update

Checklist

Please delete any irrelevant options.

My code adheres to this project's style guidelines
I have performed a self-review of my own code
I have made pertinent documentation changes
My changes do not introduce new warnings
Local unit tests pass with my changes
A pull request for updating the documentation has been submitted.

danny-avila · 2026-04-11T23:49:17Z

/gitnexus index

danny-avila · 2026-04-11T23:51:46Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 90f626231e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-04-11T23:57:25Z

@@ -903,11 +903,13 @@ export enum SearchCategories {
 export enum SearchProviders {
  SERPER = 'serper',
  SEARXNG = 'searxng',
+  TAVILY = 'tavily',


Remove unsupported Tavily search provider from enum

This adds tavily as a valid searchProvider, but the pinned runtime dependency (@librechat/agents 3.1.64 in package-lock.json) does not support it: createSearchAPI only accepts serper/searxng and throws for other values. In practice, a config using webSearch.searchProvider: tavily will pass auth selection here and then fail to construct the web_search tool at runtime.

Useful? React with 👍 / 👎.

Audited after rebasing this PR onto origin/dev and pushing a730b88e6. The runtime support for searchProvider: tavily lives in the paired agents PR (danny-avila/agents#85), so this remains a cross-repo dependency until that agents change is mergeable/published and LibreChat can bump @librechat/agents to the published version. I also updated the LibreChat Tavily option schema in a730b88e6 to match the Tavily API string modes, but I’m leaving this thread unresolved until the agents package bump is available.

Update: the original agents PR could not be updated because maintainer pushes to the contributor fork were rejected with HTTP 403, so I opened the rebased maintainer-owned replacement as danny-avila/agents#135 and closed danny-avila/agents#85. This LibreChat thread remains the same dependency issue, now tracking agents runtime support via #135.

chatgpt-codex-connector · 2026-04-11T23:57:25Z

 }

 export enum ScraperProviders {
  FIRECRAWL = 'firecrawl',
  SERPER = 'serper',
+  TAVILY = 'tavily',


Do not expose Tavily scraper before runtime support

Adding tavily to scraperProvider is currently broken with the pinned agents package: createSearchTool only has a serper branch and otherwise falls back to Firecrawl. So scraperProvider: tavily can authenticate via tavilyApiKey in this repo, but scraping actually runs through Firecrawl and requires FIRECRAWL_API_KEY, causing Tavily-only setups to fail when extraction is attempted.

Useful? React with 👍 / 👎.

Audited after rebasing this PR onto origin/dev and pushing a730b88e6. The Tavily scraper runtime support is implemented in the paired agents PR (danny-avila/agents#85), so this is still blocked on getting that agents branch pushed/merged/published and then bumping @librechat/agents here. The LibreChat branch now accepts the Tavily option modes, but this thread should stay unresolved until the runtime package dependency is available.

Update: the original agents PR could not be updated because maintainer pushes to the contributor fork were rejected with HTTP 403, so I opened the rebased maintainer-owned replacement as danny-avila/agents#135 and closed danny-avila/agents#85. This thread is still valid until #135 is merged/published and LibreChat bumps @librechat/agents.

danny-avila · 2026-05-03T21:22:19Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a730b88e6b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-05-03T21:28:29Z

@@ -927,11 +927,13 @@ export enum SearchCategories {
 export enum SearchProviders {
  SERPER = 'serper',
  SEARXNG = 'searxng',
+  TAVILY = 'tavily',


Align exported search provider type with Tavily support

Adding SearchProviders.TAVILY here makes 'tavily' valid in parsed config, but the exported SearchProvider union in packages/data-provider/src/types/web.ts still only allows 'serper' | 'searxng'. Any TypeScript consumer using SearchConfig now gets a type mismatch when configuring Tavily, which breaks type-safe adoption of the new provider unless callers cast away types.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-05-03T21:28:29Z

+#     # excludeDomains:         # Exclude specific domains from results (max 150)
+#     #   - 'spam.com'
+#     # timeRange: week         # 'day', 'week', 'month', or 'year'
+#     # timeout: 15000          # HTTP request timeout in milliseconds


Use Tavily timeout examples in seconds, not milliseconds

This example documents Tavily timeout as milliseconds (15000), but Tavily's Search/Extract timeout parameters are second-based and constrained to small ranges. Users copying this value will configure an out-of-range timeout and can trigger request validation failures. The sample should show second-based values (for example 15) and correct units in the comment.

Useful? React with 👍 / 👎.

danny-avila · 2026-05-03T22:58:02Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0f37f925a0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-05-03T23:04:37Z

-    webSearchConfig?.scraperTimeout ?? webSearchConfig?.firecrawlOptions?.timeout ?? 7500;
+    webSearchConfig?.scraperTimeout ??
+    webSearchConfig?.firecrawlOptions?.timeout ??
+    webSearchConfig?.tavilyScraperOptions?.timeout ??


Scope Tavily timeout to Tavily scraper only

tavilyScraperOptions.timeout is now part of the global scraperTimeout fallback chain, so a Tavily-specific setting can change timeout behavior even when the active scraper is firecrawl or serper. This is a behavior regression when users keep multi-provider config blocks and only switch scraperProvider: with scraperProvider: firecrawl and no explicit scraperTimeout, the Firecrawl path will inherit Tavily’s timeout unintentionally. Apply this fallback only when scraperProvider is Tavily (or require explicit scraperTimeout for cross-provider behavior).

Useful? React with 👍 / 👎.

Fixed in 1d47e5f36. tavilyScraperOptions.timeout now feeds the shared scraper timeout only when scraperProvider is Tavily, so Firecrawl and Serper no longer inherit Tavily-specific timeout settings from multi-provider config blocks. Added API web auth regression tests for both the Firecrawl and Tavily timeout paths. Local verification: npx jest src/web/web.spec.ts --runInBand.

danny-avila · 2026-05-03T23:10:50Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1d47e5f361

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-05-03T23:15:20Z

@@ -245,10 +247,23 @@ export async function loadWebSearchAuth({
    authTypes.push([category, isUserProvided ? AuthType.USER_PROVIDED : AuthType.SYSTEM_DEFINED]);
  }

+  const scraperProvider = webSearchConfig?.scraperProvider ?? 'firecrawl';


Base scraper timeout on resolved scraper provider

Use the authenticated scraper in authResult.scraperProvider when choosing provider-specific timeout options. As written, if scraperProvider is omitted in config and only Tavily credentials are available, checkAuth resolves the scraper to Tavily, but this branch still defaults to 'firecrawl' and ignores tavilyScraperOptions.timeout, falling back to 7500. That causes unexpected timeout behavior for valid Tavily-only setups and can prematurely fail extractions.

Useful? React with 👍 / 👎.

Fixed in 580a2ae08. Timeout selection now uses the resolved authResult.scraperProvider first, then falls back to the raw config/default, so Tavily-only authenticated setups get their tavilyScraperOptions.timeout even when scraperProvider is omitted. Local verification: npx jest src/web/web.spec.ts --runInBand.

danny-avila · 2026-05-03T23:18:37Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 580a2ae080

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-05-03T23:24:15Z

@@ -927,11 +927,13 @@ export enum SearchCategories {
 export enum SearchProviders {
  SERPER = 'serper',
  SEARXNG = 'searxng',
+  TAVILY = 'tavily',


Keep search-provider types consistent with Tavily support

Adding TAVILY to the runtime SearchProviders enum here without also widening the legacy SearchProvider literal type in packages/data-provider/src/types/web.ts ('serper' | 'searxng') leaves exported types inconsistent. TypeScript consumers that use SearchConfig/SearchProvider will still reject searchProvider: 'tavily', so adopting the new provider now requires unsafe casts or fails compilation.

Useful? React with 👍 / 👎.

Fixed in 3b10eb907. The legacy SearchProvider type now includes tavily, and SearchConfig includes the Tavily search key/url/options fields so TypeScript consumers can use Tavily without casts. Local verification: npx jest src/config.spec.ts --runInBand and npx tsc --noEmit in packages/data-provider.

danny-avila · 2026-05-03T23:27:34Z

@codex review

chatgpt-codex-connector · 2026-05-03T23:33:00Z

Codex Review: Didn't find any major issues. Swish!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

danny-avila · 2026-05-04T01:14:36Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9f5cdfd4c6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-05-04T01:20:54Z

@@ -7,6 +7,9 @@ export type TWebSearchKeys =
  | 'firecrawlApiKey'
  | 'firecrawlApiUrl'
  | 'firecrawlVersion'
+  | 'tavilyApiKey'


Prevent web_search uninstall from deleting Tavily tool auth

Adding tavilyApiKey to webSearchKeys causes web_search uninstall to always target TAVILY_API_KEY, and in updateUserPluginsController that key is deleted via deleteUserPluginAuth(userId, authField) without a plugin scope; deletePluginAuth then deletes by { userId, authField } only. In practice, users who configured the separate tavily_search_results_json tool (which also uses TAVILY_API_KEY) will lose that credential when uninstalling web_search, even though they did not uninstall the Tavily tool.

Useful? React with 👍 / 👎.

danny-avila · 2026-05-04T01:22:21Z

@codex review

chatgpt-codex-connector · 2026-05-04T01:28:23Z

Codex Review: Didn't find any major issues. 🚀

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

danny-avila · 2026-05-04T01:49:29Z

@codex review

chatgpt-codex-connector · 2026-05-04T01:54:14Z

Codex Review: Didn't find any major issues. Hooray!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

danny-avila · 2026-05-04T02:27:41Z

@codex review

chatgpt-codex-connector · 2026-05-04T02:34:49Z

Codex Review: Didn't find any major issues. More of your lovely PRs please.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

* feat: add Tavily integration as search provider and scraper provider * chore:update tavily web search parameters * chore:tavily paramer update * chore:update data-schemas test for tavily * fix: allow Tavily string option modes * fix: align Tavily config options * fix: scope Tavily scraper timeout * fix: use resolved scraper provider timeout * fix: widen Tavily search provider types * fix: harden Tavily web search config * fix: cap Tavily option timeouts --------- Co-authored-by: Danny Avila <danny@librechat.ai>

yashwanth-alapati marked this pull request as ready for review April 9, 2026 14:56

chatgpt-codex-connector Bot reviewed Apr 11, 2026

View reviewed changes

danny-avila force-pushed the feat/tavily-web-search branch from deb0dc1 to a730b88 Compare May 3, 2026 21:20

danny-avila changed the base branch from main to dev May 3, 2026 21:20

chatgpt-codex-connector Bot reviewed May 3, 2026

View reviewed changes

danny-avila force-pushed the feat/tavily-web-search branch from a730b88 to 0f37f92 Compare May 3, 2026 22:57

chatgpt-codex-connector Bot reviewed May 3, 2026

View reviewed changes

danny-avila force-pushed the feat/tavily-web-search branch from 3b10eb9 to 9f5cdfd Compare May 4, 2026 01:14

chatgpt-codex-connector Bot reviewed May 4, 2026

View reviewed changes

danny-avila changed the title ~~feat: add Tavily integration as search provider and scraper provider~~ feat: add Tavily as Search and Scraper Provider May 4, 2026

danny-avila changed the title ~~feat: add Tavily as Search and Scraper Provider~~ 🔍 feat: add Tavily as Search and Scraper Provider May 4, 2026

danny-avila force-pushed the feat/tavily-web-search branch from 0eaf3c5 to d90e36a Compare May 4, 2026 01:49

yashwanth-alapati added 3 commits May 4, 2026 11:26

feat: add Tavily integration as search provider and scraper provider

d9587f5

chore:update tavily web search parameters

598caee

chore:tavily paramer update

f5858ba

yashwanth-alapati and others added 8 commits May 4, 2026 11:26

chore:update data-schemas test for tavily

2a4b6c1

fix: allow Tavily string option modes

67d5cff

fix: align Tavily config options

3db2c47

fix: scope Tavily scraper timeout

2f7a6c1

fix: use resolved scraper provider timeout

9fdaff9

fix: widen Tavily search provider types

bdbf26c

fix: harden Tavily web search config

8c82100

fix: cap Tavily option timeouts

43f4298

danny-avila force-pushed the feat/tavily-web-search branch from d90e36a to 43f4298 Compare May 4, 2026 02:27

danny-avila merged commit 3da1d8c into LibreChat-AI:dev May 4, 2026
7 checks passed

Uh oh!

Conversation

yashwanth-alapati commented Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pull Request Template

Summary

Change Type

Checklist

Uh oh!

danny-avila commented Apr 11, 2026

Uh oh!

danny-avila commented Apr 11, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Apr 11, 2026

Choose a reason for hiding this comment

Uh oh!

danny-avila May 3, 2026

Choose a reason for hiding this comment

Uh oh!

danny-avila May 3, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Apr 11, 2026

Choose a reason for hiding this comment

Uh oh!

danny-avila May 3, 2026

Choose a reason for hiding this comment

Uh oh!

danny-avila May 3, 2026

Choose a reason for hiding this comment

Uh oh!

danny-avila commented May 3, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot May 3, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot May 3, 2026

Choose a reason for hiding this comment

Uh oh!

danny-avila commented May 3, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot May 3, 2026

Choose a reason for hiding this comment

Uh oh!

danny-avila May 3, 2026

Choose a reason for hiding this comment

Uh oh!

danny-avila commented May 3, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot May 3, 2026

Choose a reason for hiding this comment

Uh oh!

danny-avila May 3, 2026

Choose a reason for hiding this comment

Uh oh!

danny-avila commented May 3, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot May 3, 2026

Choose a reason for hiding this comment

Uh oh!

yashwanth-alapati commented Apr 9, 2026 •

edited

Loading