Add native Exa web search provider - #3299
Open
kesku wants to merge 1 commit into
Open
Conversation
kesku
force-pushed
the
feat/exa-web-search-provider
branch
from
July 26, 2026 20:23
10b8792 to
3175091
Compare
kesku
force-pushed
the
feat/exa-web-search-provider
branch
from
July 26, 2026 20:29
3175091 to
a8fae79
Compare
This was referenced Jul 27, 2026
This was referenced Aug 4, 2026
|
This PR has had no activity for 7 days and has been marked as stale. If you are still working on it, please push an update or leave a comment; otherwise it will be closed automatically in 7 days. |
This was referenced Aug 11, 2026
Author
|
This PR is still valid! |
This was referenced Aug 13, 2026
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.
📝 Description
Adds Exa as a native
tools.web/web_searchprovider. Requests use Exa'sPOST /searchAPI withtype: "auto"andcontents.highlights, authenticate via theX-Api-Keyheader, and support the existingd/w/m/yrange filters viastartPublishedDate. Includes config,.security.ymlkey loading, provider selection, UI settings, tests, and documentation.Enable with
tools.web.exa.enabledand an API key, or select explicitly withtools.web.provider = "exa".🗣️ Type of Change
🤖 AI Code Generation
🔗 Related Issue
#2676 (this said the MCP can be used, but now Exa will have native support in PicoClaw!)
📚 Technical Context (Skip for Docs)
SearchProviderregistry inpkg/tools/integration/web.go, using rawnet/http(no new Go module dependency). Keys rotate through the sharedAPIKeyPool.🧪 Test Environment
📸 Evidence (Optional)
Click to view Logs/Screenshots
Validation performed:
Local runtime verification:
Tool call: web_search({"count":3,"query":"site:docs.exa.ai/reference/search Exa Search API documentation"})
Tool execution started ... tool=web_search
Results for: site:docs.exa.ai/reference/search Exa Search API documentation (via Exa)
☑️ Checklist