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

Create a New Agent Class to Handle Multiple Subagents #1

Open
PaoloBova opened this issue Aug 27, 2024 · 0 comments
Open

Create a New Agent Class to Handle Multiple Subagents #1

PaoloBova opened this issue Aug 27, 2024 · 0 comments

Comments

@PaoloBova
Copy link
Owner

Issue
We need to extend the functionality of our current Agent class in agent.py to handle an arbitrary number of subagents. The new class should be able to manage and interact with these subagents, which are also instances of the Agent class.

Task
Create a new class, MultiAgent, that inherits from autogen.ConversableAgent. This class should have the following features:

Initialization: The init method should initialize the number of subagents (determined by a parameter)

Subagent Interaction: Implement methods to send and receive messages to/from the subagents. These methods should use the methods from autogen.ConversableAgent. See the Autogen documentation for more information and a tutorial on nested agents.

Knowledge Management: Each subagent has its own knowledge attribute. The MultiAgent class should have methods to update and retrieve the knowledge of its subagents. The MultiAgent needs to have it's own knowledge state that aggregates the knowledge of the subagents. Alternatively, only the multiagent has knowledge and the subagents only take on different roles when considering whether the knowledge needs to change. Part of this task is to consider which approach is better.

Acceptance Criteria

The MultiAgent class can be initialized with an arbitrary number of Agent instances.
Messages can be sent to and received from the subagents.

The knowledge of the multiagent or subagents can be updated and retrieved.

Repository owner deleted a comment Aug 27, 2024
Repository owner deleted a comment Aug 27, 2024
Repository owner locked as spam and limited conversation to collaborators Aug 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant