microsoft
Initial commit of FileSurfer in AgentChat/ext. WIP
The file surfer and the web surfer do tool calling very differently from AssistantAgent, mainly because they either have tool calls that use state or attributes of the agent itself. Though I am not certain they cant fit in the AssistantAgent template. If they can't fit, maybe we define another template for this type of agent (I could also see it being applied for the video agent and so).
Let's make sure to add some unit tests per Eric's directions https://github.com/microsoft/autogen/issues/4468 using the replay client
The file surfer and the web surfer do tool calling very differently from AssistantAgent, mainly because they either have tool calls that use state or attributes of the agent itself. Though I am not certain they cant fit in the AssistantAgent template. If they can't fit, maybe we define another template for this type of agent (I could also see it being applied for the video agent and so).
We should discuss this. This is a straight port of MagenticOne, which is perhaps the primary reason for the direct tool calling, but I'm also concerned that most of my use of tool calling it to change agent state, and this seems not to be the intention of tool calling in AssistantAgent.
@gagb , For Web and File the agents are called Surfers, but for Video it is called VideoSurferAgent. Should we rename?
Perhaps! With or without the "Agent" suffix?