Repository navigation
Add Linkup as web search provider - #301
Open
shauryajain21 wants to merge 1 commit into
Open
shauryajain21 wants to merge 1 commit into
shauryajain21 wants to merge 1 commit into
Conversation
shauryajain21
marked this pull request as ready for review
October 1, 2026 14:56
shauryajain21
force-pushed
the
add-linkup-integration
branch
from
October 2, 2026 13:45
1cc2ddd to
c81934e
Compare
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.
This pull request adds Linkup as a web search provider. It follows the same structure as the existing Exa / Tavily / LangSearch providers: it plugs into the
web_searchfallback chain and the/searchprovider picker.Integration
linkupSearchinsrc/tools/search/linkup.ts, using the officiallinkup-sdkclient (lazily initialized, likeexa.ts). It runs astandard-depth search returning 5 results, and uses the sharedparseSearchResults/formatToolResulthelpers sosourceUrlsare populated.src/tools/registry.tswhenLINKUP_API_KEYis set. It is added at the end of the chain, so the default provider order is unchanged.src/tools/search/index.ts.src/tools/search/linkup.test.ts) that covers request params, URL extraction, and error prefixing.UI and config
linkuptoSearchProviderId/SEARCH_PROVIDERSinsrc/utils/env.tsand to the provider list insrc/components/select-list.ts.LINKUP_API_KEYtoenv.exampleand the README. Keys are available at https://app.linkup.so.Usage
# .env LINKUP_API_KEY=your-linkup-api-keyThen pick Linkup with
/searchto make it the preferred provider. Otherwise it is used as a fallback after the other configured providers.Tests
bun run typecheck: passesbun test: 319 pass, 0 failweb_searchreturned 5 results with source URLs through the Linkup provider