You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
About agent actions: browse, scraper, and search
#12436
In LocalAI’s agent configuration, there is the option to select the following three “actions”:
browse
scraper
search
The questions are:
What is the actual functional difference between "browse" and "scraper"?
With which HTTP browser headers are the "browse", "scraper", and "search" actions performed?
Which search engines does "search" query? Can it be configured to use other search engines?
I’m asking question n.2 because LocalAI was also designed to ensure privacy by running AI models locally. However, a potential privacy vulnerability with local models arises from internet-based searches. Therefore, it would be important—not only to allow users to choose which search engines to use—but also to enable customization of browser headers so that LocalAI’s web requests can be “disguised” as typical browser traffic, blending in among legitimate user requests.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
In LocalAI’s agent configuration, there is the option to select the following three “actions”:
browsescrapersearchThe questions are:
"browse"and"scraper"?"browse","scraper", and"search"actions performed?"search"query? Can it be configured to use other search engines?I’m asking question n.2 because LocalAI was also designed to ensure privacy by running AI models locally. However, a potential privacy vulnerability with local models arises from internet-based searches. Therefore, it would be important—not only to allow users to choose which search engines to use—but also to enable customization of browser headers so that LocalAI’s web requests can be “disguised” as typical browser traffic, blending in among legitimate user requests.
All reactions