-
Notifications
You must be signed in to change notification settings - Fork 706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chat Copilot Planner Implementation #876
Comments
My team experienced the same issue recently, any recommendation for such scenarios? |
I am not sure exactly where we sit with regards to putting planners back into Chat Copilot using post 1.0 versions of Semantic Kernel. I'll try to find out. Are there specific things you are trying to achieve which are no longer possible? |
It was nice to see/approve/disapprove the plan before execution. This way, I felt that I had more control over the execution because the plan was not always perfectly executed i.e. certain functions from external plugins were not correctly lined up (at least that was the case with the Sequential Planner). Now, the AutoInvoke feature handles the creation and execution of a plan somewhere I don't have access and that too isn't perfect as it misses a few a functions along the way as well. So, I wanted to try out Handlebars (specifically) this time around within the context of this app, allowing me to be able edit/reuse/etc. a plan at the very least. |
@glahaye I thought about this and came out with the follwing idea. First we would have to add a boolean setting
|
@tdechanterac I would love to see that PR, yes! |
Is there any update for the enhancement, thanks. |
Hello, I noticed that the previous implementations of a planner have been removed and sk directly invokes functions from internal or external plugins. Is there any plan to implement either the Function-Calling Stepwise or the Handlebars Planner in the Chat Copilot? If not, is there an alternative planned other than the aforementioned?
Thanks!
The text was updated successfully, but these errors were encountered: