fix(agent): optimize of base agent #2276
fix(agent): optimize of base agent #2276cinjoseph wants to merge 14 commits intoeosphoros-ai:mainfrom
Conversation
… APP an Agent originates from in a cascading app scenario
6363145 to
e920421
Compare
|
ConversableAgent add name prefix, To confirm which APP an Agent originates from in a cascading app scenario。There are some questions about this modification. Agents can overload and define their own names. In theory, there is no need to add name processing including prefixes to the base class. |
|
@yhjun1026 I think the current design is based on the assumption that there is only one of each type of Agent within the same context. In my current scenario, one app can call another app, and if both apps contain the same type of Agent, I won't be able to distinguish which app an Agent comes from in places where the Agent name is displayed. I think that Agent names shouldn't be fixed or directly tied to their Roles. The Role only represents their species, but there are many different individuals within a species. It's like how we are all humans (Role), yet we have different names. |
Description
How Has This Been Tested?
Snapshots:
Include snapshots for easier review.
Checklist: