.Net Agents - ChatHistory Reducer Pattern #7570
Merged
Conversation
This file contains 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
crickman
added
PR: in progress
This was
linked to
issues
Jul 31, 2024
…/microsoft/semantic-kernel into feature_agent_history_truncation
…/microsoft/semantic-kernel into feature_agent_history_truncation
crickman
changed the title
…/microsoft/semantic-kernel into feature_agent_history_truncation
alliscode
approved these changes
Aug 7, 2024
moonbox3
approved these changes
Aug 7, 2024
crickman
removed
PR: ready for review
LudoCorporateShark
pushed a commit
to LudoCorporateShark/semantic-kernel
that referenced
this pull request
Aug 25, 2024
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Introduce ability to reduce the length of the chat-history when using the _Agent Framework_. A prolonged agent dialog can exceed the allowed token limit. As such, introducing a technique for managing chat-history is critical. Such a technique must be available for both `AgentChat` and _No-Chat_ invocation modes. > Note: This consideration only applies to `ChatCompletionAgent` as the Assistant API manages this internally for `OpenAIAssistantAgent`. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> - Define `IChatHistoryReducer` contract - Add `ChatCompletionAgent.HistoryReducer` nullable/optional property - Update `ChatCompletionAgent.GetChannelKeys()` to assign agents to dedicted channels based on reducer. - Implement "Top N" truncating reducer: `ChatHistoryTruncationReducer` - Implement summarizing reducer: `ChatHistorySummarizationReducer` - Allow prompt customization for `ChatHistorySummarizationReducer` - Update `ChatHistoryChannel` to make use of agent-reducer, if present - Add `ChatCompletion_HistoryReducer` sample under _Concepts_ ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [X] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 😄
4 tasks
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
Introduce ability to reduce the length of the chat-history when using the Agent Framework.
A prolonged agent dialog can exceed the allowed token limit. As such, introducing a technique for managing chat-history is critical. Such a technique must be available for both
AgentChatand No-Chat invocation modes.Description
IChatHistoryReducercontractChatCompletionAgent.HistoryReducernullable/optional propertyChatCompletionAgent.GetChannelKeys()to assign agents to dedicted channels based on reducer.ChatHistoryTruncationReducerChatHistorySummarizationReducerChatHistorySummarizationReducerChatHistoryChannelto make use of agent-reducer, if presentChatCompletion_HistoryReducersample under ConceptsContribution Checklist