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
Following the discussion of use Kernel as preferred method as it enable a set of relevant features it's clear, in my mind, that the framework should offer a stronger management of conversation and specifically ChatHistory. It's necessary for me to offer a way to use invokeXXXasynk using history as a parameter as is so clear that lack of this push developers to us IChatCompletionServices instead Kernel as you can see in almost all your samples. In alternative you could consider to offer an extention in ChatHistory that expose history as a sequence of as you have a parser to extract it. In my mind should be important to avoid unnecessary back and forward
The text was updated successfully, but these errors were encountered:
Following the discussion of use Kernel as preferred method as it enable a set of relevant features it's clear, in my mind, that the framework should offer a stronger management of conversation and specifically ChatHistory. It's necessary for me to offer a way to use invokeXXXasynk using history as a parameter as is so clear that lack of this push developers to us IChatCompletionServices instead Kernel as you can see in almost all your samples. In alternative you could consider to offer an extention in ChatHistory that expose history as a sequence of as you have a parser to extract it. In my mind should be important to avoid unnecessary back and forward
The text was updated successfully, but these errors were encountered: