Codecov Report

Attention: Patch coverage is 96.19048% with 4 lines in your changes missing coverage. Please review.

Project coverage is 70.61%. Comparing base (0363388) to head (451757f).
Report is 5 commits behind head on main.

@@            Coverage Diff             @@
##             main    #5071      +/-   ##
==========================================
+ Coverage   69.91%   70.61%   +0.70%     
==========================================
  Files         168      174       +6     
  Lines       10698    11111     +413     
==========================================
+ Hits         7479     7846     +367     
- Misses       3219     3265      +46     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Some updates on this effort on here so we can have a broader discussion.

There are a few current issues with making teams declarative (or more generally - elements that inherit from a protocol cannot be declarative in the current setup without mypy/build errors).

The short story is that:

• the inheritance structure for Agents is ChatAgent ->BaseChatAgent -> AssistantAgent.
  • ChatAgent is a protocol .. it cannot be declarative/component as it can only inherit from protocols
  • BaseChatAgent is an abstract class and can be made a component .. so this is where component behaviors for agents begin
• Teams (e,g RoundRobinGroupChat, Selector ...) have a participants arg which is typed as List[ChatAgent]
  • However, when we serialize/deserialize we can only return BaseChatAgent classes
    Mypy/pyright throw errors ... ChatAgent does not have dump_component etc

Similar situation with SocietyofMindAgent. It has a team field that inherits from the Team protocol. While we can serialize base Team classes, mypy still fails as the Team protocol itself cannot cannot inherit from ComponentBase.

Some potential solutions/directions

• update participants type to List[BaseChatAgent] instead of ChatAgent (has its own issues)
• Make ChatAgent an abstract class - not a protocol ...(seems we mix protocol and base class inheritance a few times in agentchat ...)
• Modify Component config design to accomodate Protocol?
• Something else ..

@ekzhu , @jackgerrits

Just a comment on the name. This work is not to make agent chat declarative -- the agentchat API is already declartive.

It is to make the configuration serializable. So should update the title and fix how we mention it for precise language.