there should be support for more agent oriented search engines that provide structured results and are not blocked as robots. serper (serper.dev), tavily, brave search and duckducksearch in addition to the already implemented google search via browser control should be supported.
this should be configureable in the preferences, which is used to get results. this should not introduce new tools, it should just define what backend we use for searching. The additional metadata that some of the interfaces return should be supported - they will be empty with some of the services, but that is fine.
The user must be able to order the different services, so that when multiple services are supported and one is not working due to for example request volume, the system can fall down to the next.
there should be support for more agent oriented search engines that provide structured results and are not blocked as robots. serper (serper.dev), tavily, brave search and duckducksearch in addition to the already implemented google search via browser control should be supported.
this should be configureable in the preferences, which is used to get results. this should not introduce new tools, it should just define what backend we use for searching. The additional metadata that some of the interfaces return should be supported - they will be empty with some of the services, but that is fine.
The user must be able to order the different services, so that when multiple services are supported and one is not working due to for example request volume, the system can fall down to the next.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
there should be support for more agent oriented search engines that provide structured results and are not blocked as robots. serper (serper.dev), tavily, brave search and duckducksearch in addition to the already implemented google search via browser control should be supported.
this should be configureable in the preferences, which is used to get results. this should not introduce new tools, it should just define what backend we use for searching. The additional metadata that some of the interfaces return should be supported - they will be empty with some of the services, but that is fine.
The user must be able to order the different services, so that when multiple services are supported and one is not working due to for example request volume, the system can fall down to the next.
we stick with the browser based search right now, that does the job for what we need right now.