langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Knowledge tool for the node agent #12899

New Issue
Closed
opened 2026-02-21 19:09:35 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:09:35 -05:00
Owner
Copy Link
Copy Source

Originally created by @juniorsereno on GitHub (Apr 14, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

It would have the possibility to include knowledge retrieval as a tool for the agent node or as it is done in the agent app where the agent generates the query for the knowledge search and also decides the moment to pull the knowledge.

There is a serious problem using the knowledge node with user.query because it fetches all the time and fills the agent with random information at that moment, causing hours of adjustment to the knowledge

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @juniorsereno on GitHub (Apr 14, 2025). ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. It would have the possibility to include knowledge retrieval as a tool for the agent node or as it is done in the agent app where the agent generates the query for the knowledge search and also decides the moment to pull the knowledge. There is a serious problem using the knowledge node with user.query because it fetches all the time and fills the agent with random information at that moment, causing hours of adjustment to the knowledge ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement🔨 feat:tools labels 2026-02-21 19:09:35 -05:00
yindo closed this issue 2026-02-21 19:09:35 -05:00
yindo commented 2026-02-21 19:09:36 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 15, 2025):

Hi, @juniorsereno. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • Proposal to add a knowledge retrieval tool for the node agent to improve query handling and timing.
  • Current method results in continuous fetching of irrelevant data, requiring adjustments.
  • You mentioned no interest in contributing to the development of this feature.
  • No further comments or activity have been made on this issue.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If there is no response, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (May 15, 2025): Hi, @juniorsereno. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - Proposal to add a knowledge retrieval tool for the node agent to improve query handling and timing. - Current method results in continuous fetching of irrelevant data, requiring adjustments. - You mentioned no interest in contributing to the development of this feature. - No further comments or activity have been made on this issue. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of the Dify repository by commenting here. - If there is no response, the issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement 🔨 feat:tools
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#12899
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?