Hi @suntp! I'm Dosu and I’m helping the dify team.

You've correctly identified a real issue: in Agent mode, manual metadata filtering does not take effect when specifying input variables because the system uses the display name instead of the variable name for filtering. This mismatch prevents the input from matching documents in the knowledge base as expected.

This is a known limitation in Dify Agent applications. The Agent application was originally designed to support only external data tools and did not include the necessary code for knowledge base retrieval and metadata filtering, unlike Chatflow mode. As a result, metadata filtering in Agent mode has not worked as intended in past versions, including 1.4.1. There is a related discussion and confirmation of this limitation, along with a temporary fix provided in PR #19020 (issue reference).

The root cause is that the metadata filtering condition is identified by a name field in the code, which appears to be mapped to the display name in Agent mode, rather than the variable name as in Chatflow mode. This difference leads to the filtering not working as expected when input variables are specified.

A recent fix has addressed a related issue where the metadata_condition parameter was not being used for non-external providers, causing metadata filtering to fail in both chatbot and workflow implementations. This has now been acknowledged and fixed by the Dify team (details here).

What you can do:

• If you are able to update your deployment, check if the temporary fix from PR fix: metadata filter not work #19020 resolves your issue.
• As you suggested, changing the metadata filtering variable setting in Agent mode to use the variable name (instead of the display name) should resolve the mismatch and allow filtering to work as expected.

If you need more details on how to apply the fix or where to make the change, let me know!

To reply, just mention my name @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

There is still a bug in the web interface: even if a variable is specified, the option still displays Constant.

hi，I've already identified the location of the problematic code and fixed it locally, as shown in the image below. Am I allowed to submit the code to resolve this bug? @crazywoola @JohnJyong