You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
.Net Agents - Investigate extensibility of ChatCompletionAgent for purposes of history management / truncation #7416
Until we can formally support truncation for all users of the Agent Framework, it is important to provide a timely solution for Industry AI to address this as part of their Copilot SDK when using AgentChat.
Unsealing ChatCompletionAgent may be one part of the solution here, but more critically: what is the appropriate articulation point to manage a truncation strategy for the history?
Chris (@crickman) From our investigation it seems like the method CreateChannelAsync inside ChatHistoryKernelAgent should be unsealed and not internal, and the same for InvokeAsync inside ChatHistoryChannel.
If ChatCompletionAgent will be unsealed as well it could improve our implementation.
Activity
EdenTanami commentedon Jul 24, 2024
Chris (@crickman) From our investigation it seems like the method CreateChannelAsync inside ChatHistoryKernelAgent should be unsealed and not internal, and the same for InvokeAsync inside ChatHistoryChannel.
If ChatCompletionAgent will be unsealed as well it could improve our implementation.