-
Notifications
You must be signed in to change notification settings - Fork 795
.NET: Add per run / thread feature collection support and improved custom ChatMessageStore support #2354
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
Draft
westey-m
wants to merge
4
commits into
main
Choose a base branch
from
feature-featurecollections-messagestore
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…stom ChatMessageStore support (#2345) * Add the ability to override services on an agent per run. * Remove Run from AgentFeatureCollection name. * Adding features param to GetNewThread. * Move feature collection. * Add features to DeserializeThread * Remove servicecollection based option * Add feature collection unit tests and fix bug identified in code review. * Add more unit tests for DelegatingAIAgent and AgentRunOptions * Fix formatting. * Address PR comments. * Switch to dedicated ConversationIdAgentFeature and improve 3rd party storage samples. * Fix bug in sample.
stephentoub
reviewed
Nov 20, 2025
dotnet/src/Microsoft.Agents.AI.Abstractions/Features/AgentFeatureCollection.cs
Outdated
Show resolved
Hide resolved
stephentoub
reviewed
Nov 20, 2025
dotnet/src/Microsoft.Agents.AI.Abstractions/Features/AgentFeatureCollection.cs
Outdated
Show resolved
Hide resolved
stephentoub
reviewed
Nov 20, 2025
dotnet/src/Microsoft.Agents.AI.Abstractions/Features/AgentFeatureCollection.cs
Outdated
Show resolved
Hide resolved
stephentoub
reviewed
Nov 20, 2025
dotnet/src/Microsoft.Agents.AI.Abstractions/Features/AgentFeatureCollection.cs
Outdated
Show resolved
Hide resolved
stephentoub
reviewed
Nov 20, 2025
dotnet/src/Microsoft.Agents.AI.Abstractions/Features/AgentFeatureCollection.cs
Outdated
Show resolved
Hide resolved
stephentoub
reviewed
Nov 20, 2025
dotnet/src/Microsoft.Agents.AI.Abstractions/Features/AgentFeatureCollection.cs
Outdated
Show resolved
Hide resolved
* Update AgentFeatureCollections with feedback * Address feedback. * Fix issue with sample. * Change generic type restriction to notnull * Remove revision * Update dotnet/src/Microsoft.Agents.AI.Abstractions/Features/AgentFeatureCollectionExtensions.cs Co-authored-by: Copilot <[email protected]> * Add revision back again and improve some formatting. * Remove virtual from revision. * Add overloads taking type as param and add unit tests. --------- Co-authored-by: Copilot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
Today there isn't good support for scenarios where chat history is stored in a custom store and a developer wants to bootstrap new threads with the existing data. There also isn't good support for cases where a host application may want to override any chat history storage that an agent uses, to better support the protocol that the agent is exposed via.
#2325
Description
Contribution Checklist