Skip to content
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

Agency research instead of commands #503

Closed
1 task done
thejerome1502 opened this issue Apr 8, 2023 · 2 comments
Closed
1 task done

Agency research instead of commands #503

thejerome1502 opened this issue Apr 8, 2023 · 2 comments
Labels
needs discussion To be discussed among maintainers Stale

Comments

@thejerome1502
Copy link

Duplicates

  • I have searched the existing issues

Summary 💡

Replace Google Search by an agency (coop of agents) to search both Google and pinecone memory from a prompt sent by autogpt to this agency

Uses multiple instances of a GPT-3.5 model to generate tags for each search engine (e.g., Pinecone and Google) based on the user prompt.
Uses the generated tags to query Pinecone database and Google Search API for the top results relevant to the user prompt.
Uses a GPT-3.5 summarization and organization model to identify the top 5 most relevant search results from Pinecone database and Google Search API, respectively.
Uses a GPT-3.5 summarization and organization model to summarize and organize the search results from Pinecone database and Google Search API in relevance to the user prompt.
Combines the summarized and organized search results from both sources using a GPT-3.5 model.
Outputs it to autogpt

Examples 🌈

No response

Motivation 🔦

No response

@Pwuts Pwuts added the needs discussion To be discussed among maintainers label Apr 18, 2023
@Boostrix
Copy link
Contributor

Boostrix commented May 4, 2023

my 2c: supporting multiple search engines does sound like a good idea (after all, additional search engines would also be a contigency for agents/tasks to try other options), ideally those with an API and a way to return results in a suitable format like JSON/XML - also, being able to search headless without requiring a headless browser would be useful, just the equivalent of curl/wget (wrapped via Python) should suffice ideally

Also, a number of folks mentioned issues relating to browse_website that would not actually conduct a proper search in a looped fashion - i.e. where it would use variations of search term queries and recursively research a topic in order to gather relevant websites and additional keywords. More often than not, "bootstrapping a [re]search" via something like wikipedia is also a good way to get research going. #3635

Realistically, browse_website probably needs to be turned into a plugin and extended - there are a bunch of related RFEs, we probably need some sort of "meta" issue for it:

@github-actions
Copy link
Contributor

This issue was closed automatically because it has been stale for 10 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs discussion To be discussed among maintainers Stale
Projects
None yet
Development

No branches or pull requests

3 participants