Treat a "chat" as a "Chat Workflow" that can include single agents, multiple agents, or nested chats.
Implementing a wrapper class/interface that maintains consistent input and output signatures will enable more complex and structured interactions, enhancing the overall functionality of the SK Agent SDK.
This will enable that we can "swap" any Agent taking part on a conversation by a full chat (nested chat). Just a wrapper with the same interface, but internally its input and output are redirected to a "chat workflow" instead of an Agent.
Treat a "chat" as a "Chat Workflow" that can include single agents, multiple agents, or nested chats.
Implementing a wrapper class/interface that maintains consistent input and output signatures will enable more complex and structured interactions, enhancing the overall functionality of the SK Agent SDK. This will enable that we can "swap" any Agent taking part on a conversation by a full chat (nested chat). Just a wrapper with the same interface, but internally its input and output are redirected to a "chat workflow" instead of an Agent.
I believe this is clean and simple. Thoughts?