-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add search engine feature #7262
base: main
Are you sure you want to change the base?
Conversation
… use when providing context to the LLM.
…sary (All-Hands-AI#6618) Co-authored-by: openhands <openhands@all-hands.dev>
Co-authored-by: openhands <openhands@all-hands.dev> Co-authored-by: Xingyao Wang <xingyao6@illinois.edu>
…dates (All-Hands-AI#6617) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: amanape <83104063+amanape@users.noreply.github.com>
Co-authored-by: sp.wack <83104063+amanape@users.noreply.github.com>
Co-authored-by: openhands <openhands@all-hands.dev> Co-authored-by: Ray Myers <ray.myers@gmail.com>
@OpenHands please do the following:
|
Openhands is working, @neubig can track my progress at all-hands.dev |
@OpenHands add user-facing documentation of this feature. It should be included in the "Advanced Configuration" section of the docs. Please view other pages in that section and understand the structure and content of other similar docs, then add some docs for this feature. You can keep it concise, no need to be overly wordy. |
Openhands is working, @neubig can track my progress at all-hands.dev |
Co-authored-by: Boxuan Li <liboxuan@connect.hku.hk>
Co-authored-by: Boxuan Li <liboxuan@connect.hku.hk>
What is the current progress with this and search engines (e.g. SearXNG or Startpage or Qwant)? |
@BradKML I think this PR itself is working.. The reason we haven't merge this is that this adds yet another potential env var we need to worry about (i.e., SEARCH ENGINE API KEY) that may complicate the user experience (user need to input yet another key to use OpenHands) OR the developer experience (if we want to automatically turn off search IF user didn't provide the key). I'm thinking if this can be taken care of by the MCP (#7637) that will give us search engine & other things, and we can just implement these "selective turn off when no API key is provided" in one place |
This PR adds a search engine feature to OpenHands.
Changes:
Tests:
Fix: #7262