[Agent] Introduce policies #1572
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR aims to introduce the support for "policies" at the
Agentlevel, Policies are a way to enable/disable features in agents (think of it like stamps onMessengermessages` or "feature-flags").This PR is an extension of a discussion with @chr-hertel last week about the refactoring of
Agent, the main goal is to allow adding new features depending on the configuration of an agent and the enabled policies (for example, we might want to enableSpeechPolicyto add the support for Speech as implemented in #943, it can also help the introduction ofEvaluatorlater and many more).For now, the
DelayPolicyis added to show how the code is added into the component, the goal of this policy is to add a delay before/after sending/receiving the input/output.PS: The code is decoupled from input/outputs processors.