-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
.Net: Change Agents.Abstractions to depend on SemanticKernel.Abstractions instead of SemanticKernel.Core #10574
.Net: Change Agents.Abstractions to depend on SemanticKernel.Abstractions instead of SemanticKernel.Core #10574
Conversation
dotnet/src/SemanticKernel.Abstractions/Functions/KernelFunctionNoop.cs
Outdated
Show resolved
Hide resolved
1d60afe
to
5dbacd7
Compare
Waiting on feedback from @crickman |
…clude template directives
526e70c
to
45eebf5
Compare
4ca8ba0
to
f159c49
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feels like we're still missing the case were an Azure Agent or Assistant was created with a template and the rehydrated from an existing model/definition via retrieval by its identifier.
In that case, would the developer be expected to also provide the full template config?
What would be the behavior when the provided template config doesn't match this existing definition?
This case needs to be handled as part of the declarative agent framework. My initial thought is that it should be possible to override instructions, provide additional tools, etc for an already deployed agent. Overriding instructions will be useful if the template contains values that are related to the current request. |
87c849d
to
50e4213
Compare
Motivation and Context
Closes #10571
Description
Contribution Checklist