Add Exa as a search backend - #263
Open
kesku wants to merge 1 commit into
Open
Conversation
kesku
force-pushed
the
kesku/add-exa-support
branch
from
July 30, 2026 23:06
d59cdf4 to
4d4c02f
Compare
kesku
force-pushed
the
kesku/add-exa-support
branch
from
July 30, 2026 23:07
4d4c02f to
79005bb
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
1 participant
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.
Hi! Right now the
searchtool is wired to Serper only. This PR adds Exa as an optional backend so folks can use semantic web search instead (or as a Plan B if they don't have a Serper key).What changed
exa_search()ininference/tool_search.py, same result shape as the existing Serper pathSEARCH_PROVIDER=exa(Serper stays the default)EXA_API_KEYis set, it falls back to Exa automatically.env.exampleupdatedUsage
Existing Serper setups keep working as-is. Happy to tweak anything if you'd like this shaped differently!