Open mknio opened 7 months ago
@thinkall would you like to make RetrievalUserProxyAgent more general? If the agent is intended for general use, "problem" is probably too narrow a concept. Another question I've been thinking is how to consolidate TeachableAgent, RetrievalUserProxyAgent, EcoAssistant, MemGPT etc. I believe there is value to generalize the lessons learned from these and build a good systems component. cc @rickyloynd-microsoft @JieyuZ2 @cpacker
I have seen some other codes where it uses message and somewhere else it uses "problem" and "message". So the question rises. When do we use "message" and when do we use "problem". the code is from the examples that autogen provided in the agentchat_groupchat_RAG.ipynb. Thank you
@thinkall would you like to make RetrievalUserProxyAgent more general? If the agent is intended for general use, "problem" is probably too narrow a concept. Another question I've been thinking is how to consolidate TeachableAgent, RetrievalUserProxyAgent, EcoAssistant, MemGPT etc. I believe there is value to generalize the lessons learned from these and build a good systems component. cc @rickyloynd-microsoft @JieyuZ2 @cpacker
it may require a modularized way to build retrieval-based agents, define store and retrieve function like we define reply function.
@thinkall would you like to make RetrievalUserProxyAgent more general? If the agent is intended for general use, "problem" is probably too narrow a concept. Another question I've been thinking is how to consolidate TeachableAgent, RetrievalUserProxyAgent, EcoAssistant, MemGPT etc. I believe there is value to generalize the lessons learned from these and build a good systems component. cc @rickyloynd-microsoft @JieyuZ2 @cpacker
it may require a modularized way to build retrieval-based agents, define store and retrieve function like we define reply function.
Yes, looks like it's time to start working on that.
I have seen some other codes where it uses message and somewhere else it uses "problem" and "message". So the question rises. When do we use "message" and when do we use "problem". the code is from the examples that autogen provided in the agentchat_groupchat_RAG.ipynb. Thank you
Hi @mknio , before we update the code, you'll need to initiate the chat with problem
when using a RetrieveUserProxyAgent.
Isnt "message" the better word to use in this instance as it is also dependent on many other factors like the generate_init_message and initiate_chat are all expecting message. Anyways, I will change the code to "problem" once it is updated if that is the most suitable thing to do. Thank you!
Isnt "message" the better word to use in this instance as it is also dependent on many other factors like the generate_init_message and initiate_chat are all expecting message. Anyways, I will change the code to "problem" once it is updated if that is the most suitable thing to do. Thank you!
Right, we'll unify the interface. Before that, please use "problem" as a workaround. Just to clarify, you need "problem" for the current version of RetrieveUserProxyAgent.
I am trying to use the Autogen's RetrievalUserProxy and after i created a userpoxyagent and an assistant agent i wanted to initiate a message by saying user.initiate_chat(assistant, message = passed_prompt). it gave me a TypeError that it is not expecting it because it should have been passed as "problem" not "message" in the retrieval_user_proxy_agent.py at line 414. It is passed as a "problem" not a "message".
However, in the class ConversableAgent the initiate_chat function is expecting a message argument at the line 529.
I believe that the generate_init_message should be also overridden as message and not as problem.
Please clarify this issue.