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

Please increase the limit of tools we can use to min 10 plus if possible give us option to test and use higher number of tools without any limits #1061

New Issue
Closed
opened 2026-02-21 17:29:46 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 17:29:46 -05:00
Owner
Copy Link
Copy Source

Originally created by @Greatz08 on GitHub (Feb 18, 2024).

Self Checks

1. Is this request related to a challenge you're experiencing?

only 5 tools are not sufficient, i have read one comment regarding this only but he closed his issue so i am opening it myself, please give user the chance to select more number of tools. DO NOT PUT LIMITATION ON IT EVEN IF PERFORMANCE MIGHT NOT BE GREAT. just put disclaimer that if you use more tools you might see tools conflict with each other and provide bad response, So its upto user if he wanna try more tools or not donot put limits by yourself because with time i believe we will understand what things and in what way conflict and how we can prevent that so yeah i hope in next upcoming version you will remove those limits and i know its not tough thing to remove those limits from code base but still the way i told you to handle this is much better then limiting users :-)
Again Thankyou very much for this awesome solution

2. Describe the feature you'd like to see

:-)

3. How will this feature improve your workflow or experience?

:-)

4. Additional context or comments

No response

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Greatz08 on GitHub (Feb 18, 2024). ### 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 file this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). ### 1. Is this request related to a challenge you're experiencing? only 5 tools are not sufficient, i have read one comment regarding this only but he closed his issue so i am opening it myself, please give user the chance to select more number of tools. DO NOT PUT LIMITATION ON IT EVEN IF PERFORMANCE MIGHT NOT BE GREAT. just put disclaimer that if you use more tools you might see tools conflict with each other and provide bad response, So its upto user if he wanna try more tools or not donot put limits by yourself because with time i believe we will understand what things and in what way conflict and how we can prevent that so yeah i hope in next upcoming version you will remove those limits and i know its not tough thing to remove those limits from code base but still the way i told you to handle this is much better then limiting users :-) Again Thankyou very much for this awesome solution ### 2. Describe the feature you'd like to see :-) ### 3. How will this feature improve your workflow or experience? :-) ### 4. Additional context or comments _No response_ ### 5. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 17:29:46 -05:00
yindo closed this issue 2026-02-21 17:29:46 -05:00
yindo commented 2026-02-21 17:29:47 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 18, 2024):

🤖

Based on the context provided, it seems that there has been a similar request in the past to increase the number of tools allowed in an agent app. The solution suggested was to change the value of MAX_TOOLS_NUM in the config file to the desired number. However, it was also noted that increasing the limit might affect the performance and layout of the application, so it should be done with caution.

Here is the relevant code snippet from the issue:

# config.py
MAX_TOOLS_NUM = 10  # Increase this value to the desired number

Regarding your request to have the option to test and use a higher number of tools without any limits, this might be a more complex feature to implement. It would require careful consideration of the potential performance implications and conflicts between tools. It might also require changes to the user interface to accommodate a larger number of tools.

As for adding a disclaimer warning users about potential conflicts when using more tools, this seems like a reasonable suggestion. It could be implemented as a pop-up warning or a note in the documentation.

Please note that these changes would need to be implemented by the maintainers of the dify repository. As an AI, I'm unable to make these changes myself. However, I hope this information is helpful and addresses your request. If you have any further questions or need more clarification, feel free to ask.

For more information, you can refer to the solved issue: Increase the number of tools allowed in an agent app.

Sources

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot[bot] commented on GitHub (Feb 18, 2024): _🤖_ <!-- Answer --> Based on the context provided, it seems that there has been a similar request in the past to increase the number of tools allowed in an agent app. The solution suggested was to change the value of `MAX_TOOLS_NUM` in the config file to the desired number. However, it was also noted that increasing the limit might affect the performance and layout of the application, so it should be done with caution. Here is the relevant code snippet from the issue: ```python # config.py MAX_TOOLS_NUM = 10 # Increase this value to the desired number ``` Regarding your request to have the option to test and use a higher number of tools without any limits, this might be a more complex feature to implement. It would require careful consideration of the potential performance implications and conflicts between tools. It might also require changes to the user interface to accommodate a larger number of tools. As for adding a disclaimer warning users about potential conflicts when using more tools, this seems like a reasonable suggestion. It could be implemented as a pop-up warning or a note in the documentation. Please note that these changes would need to be implemented by the maintainers of the dify repository. As an AI, I'm unable to make these changes myself. However, I hope this information is helpful and addresses your request. If you have any further questions or need more clarification, feel free to ask. For more information, you can refer to the solved issue: [Increase the number of tools allowed in an agent app.](https://github.com/langgenius/dify/issues/2429) ## Sources - [Increase the number of tools allowed in an agent app.](https://github.com/langgenius/dify/issues/2429) <!-- Dosu Comment Footer --> <details open> <summary> #### About Dosu </summary> This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. </details>
yindo commented 2026-02-21 17:29:47 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 18, 2024):

duplicate https://github.com/langgenius/dify/issues/2429

The limit of tools is set in order to get a better performance of Agent, in the ReAct agent mode, a long tool list could lead a context pollution.

@crazywoola commented on GitHub (Feb 18, 2024): duplicate https://github.com/langgenius/dify/issues/2429 > The limit of tools is set in order to get a better performance of Agent, in the ReAct agent mode, a long tool list could lead a context pollution.
yindo commented 2026-02-21 17:29:47 -05:00
Author
Owner
Copy Link
Copy Source

@Greatz08 commented on GitHub (Feb 18, 2024):

@crazywoola i mentioned it is duplicated but this issue is solved yet i have most recent version and in that i can use only 5 tools at a time not more than that and the one this is duplicated of is also closed by user idk why so please reopen it and increase the limit

@Greatz08 commented on GitHub (Feb 18, 2024): @crazywoola i mentioned it is duplicated but this issue is solved yet i have most recent version and in that i can use only 5 tools at a time not more than that and the one this is duplicated of is also closed by user idk why so please reopen it and increase the limit
yindo commented 2026-02-21 17:29:47 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 18, 2024):

I do quote one thread.

The limit of tools is set in order to get a better performance of Agent, in the ReAct agent mode, a long tool list could lead a context pollution.

@crazywoola commented on GitHub (Feb 18, 2024): I do quote one thread. > The limit of tools is set in order to get a better performance of Agent, in the ReAct agent mode, a long tool list could lead a context pollution.
yindo commented 2026-02-21 17:29:47 -05:00
Author
Owner
Copy Link
Copy Source

@Yeuoly commented on GitHub (Feb 20, 2024):

done. #2497

@Yeuoly commented on GitHub (Feb 20, 2024): done. #2497
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
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#1061
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?