feat: Knowledge advanced filtering #5223
Open
+991
−282
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
willemcdejongh
force-pushed
the
knowledge-advanced-filtering
branch
2 times, most recently
from
66acbac to
7a17d27
Compare
kausmeows
reviewed
Oct 29, 2025
kausmeows
reviewed
Oct 29, 2025
There was a problem hiding this comment.
We should also add unit tests using all for these
kausmeows
reviewed
Oct 29, 2025
| return {"op": "IN", "key": self.key, "values": self.values} | ||
|
|
||
|
|
||
| class GT(FilterExpr): |
There was a problem hiding this comment.
What does LT and GT mean? I'm a bit out of loop but maybe lets add a comment too
(edit- ok got it, greater than/less than)
There was a problem hiding this comment.
We should really add docstrings and in general document this well
dirkbrnd
reviewed
Nov 3, 2025
There was a problem hiding this comment.
I think these should be at a higher level than knowledge, so /agno/filters.py
There was a problem hiding this comment.
Ruan had a similar comment, but we moved it to agno/utils
dirkbrnd
reviewed
Nov 3, 2025
willemcdejongh
force-pushed
the
knowledge-advanced-filtering
branch
3 times, most recently
from
f77fc53 to
1327bb6
Compare
willemcdejongh
force-pushed
the
knowledge-advanced-filtering
branch
from
1327bb6 to
528b035
Compare
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.
Summary
This PR introduces advanced filtering capabilities for Knowledge searches, enabling developers to filter knowledge base results using expressive filter conditions. Users can now apply metadata-based filters using operators like EQ, IN, NOT, AND, and OR to create precise, targeted knowledge searches.
Key Features:
Filter expressions DSL with support for equality, inclusion, and logical operators
Integration with vector databases (PgVector, SurrealDB, etc.)
Support for filtering at Agent, Team, and Workflow levels
Comprehensive cookbook examples demonstrating filter usage
Related to: Enhanced knowledge search and retrieval capabilities
Key Changes
Added filter expression classes:
EQ(key, value) - Equality comparison
IN(key, values) - Check if value is in list
GT(key, value) / LT(key, value) - Greater than/Less than comparisons
NOT(condition) - Logical negation
AND(*conditions) / OR(*conditions) - Logical combinations
Updated pgvector.py to translate filter DSL to SQLAlchemy queries
Fixed type annotations (ColumnElement[bool] instead of BinaryExpression)
Added filter support for hybrid and vector searches
Added knowledge_filters parameter to search methods
Support for filtering in Agent, Team, and Workflow classes
cookbook/knowledge/filters/filtering_with_conditions_on_agent.py
cookbook/knowledge/filters/filtering_with_conditions_on_team.py
Type of change
Checklist
./scripts/format.shand./scripts/validate.sh)Additional Notes
Add any important context (deployment instructions, screenshots, security considerations, etc.)