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
Ignore Some Messages When Transforming #2661
Merged
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
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.
Why are these changes needed?
This PR implements some utilities that can be useful when applying
TransformMessages
toGroupChatManager
. This is also part 1 of 2.The changes in this PR allow specific messages to be included or excluded during the transformation process based on user-defined criteria.
filter_configs
was improved so the user can have finer control when filtering configs. If the user decides toexclude=False
(default), then whichever config matches thefilter_dict
will be returned (the behavior that is currently in main). Ifexclude=True
then the opposite happens; whichever config matches thefilter_dict
will be excluded from the final result.Some transforms like
TextMessageCompressor
andMessageTokenLimiter
can use thefilter_dict
concept present in autogen to ignore some messages from being transformed.Example:
filter_dict={"role": ["system"]}, exclude=True
.filter_dict={"name": ["compress_me_agent"]}, exclude=False
.Future Work:
PrefixName
transform: Prepends every message with a text template, e.g. "The agent {agent_name} said this:". It is useful when API providers don't use thename
key in the message.FilterMessage
: Drops all messages based on thefilter_dict
you pass in. E.g. we want to drop all system messages from the context.Related issue number
Checks