Repository navigation
feat(browsecomp): add Brave search provider - #3503
konarkmodi wants to merge 1 commit into
Conversation
|
Thanks for the contribution, and sorry it sat without a response for so long. Two things: (1) the branch is 682 commits behind |
|
@konarkmodi Can you also run Browsecomp with Brave as the search provider on the superV3.5 GA and the GLM 5.3 as well? |
Thank you @marcromeyn, updated the branch from |
8ac9034 to
c7661d8
Compare
Signed-off-by: Konark Modi <konarkmodi@tesseracted.com>
c7661d8 to
9ba25de
Compare
What does this PR do?
This PR adds Brave Search as an opt-in BrowseComp search provider using Brave's public
LLM Context API.
Brave Search makes the LLM Context request and persists the returned URL context
in a per-session cache under
/tmp. The existing Browse tool signature isretained for agent compatibility; Brave Browse serves matching URLs from that
cache and does not make a second provider request. There is no separate private
Brave extraction API call.
Tavily and Exa remain unchanged and continue to provide the existing defaults.
Transparency note: I contributed to this work as a part-time consultant for Brave through Tesseracted Labs GmbH.
Validation
Ran against the final diff:
The targeted pre-commit checks passed. The pytest suite was not run locally
because pytest is not installed in the environment.
Rollouts
Evaluated BrowseComp with:
gpt-4.1-2025-04-14nvidia/NVIDIA-Nemotron-3-Ultra-550B-A55B-NVFP4Compatibility and benchmark impact
representative benchmark evidence.
Checklist
pre-commit run --all-files) (so CI lint/format checks pass).git commit -s) (so the DCO check passes).