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

Extend Tool/Plugin Support to Include Chatbots, Agents, and Workflows #3408

New Issue
Closed
opened 2026-02-21 17:57:26 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:57:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @sunxichen on GitHub (May 16, 2024).

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).
  • Please do not modify this template :) and fill in all the required fields.

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

Yes, currently, Dify allows only functions (built-in or custom) to be used as tools (plugins) for the large language model. However, I face a limitation where I cannot integrate pre-built chatbots, agents, or orchestrated workflows as tools. This missing capability hinders the full potential of creating modular and collaborative Agent solutions, especially in scenarios where multi-agent cooperation is paramount.

2. Describe the feature you'd like to see

I would like to request an enhancement to Dify that extends the existing 'Tools' architecture to accommodate not just functions but also chatbots, agents, and workflows. The vision is to enable users to package their standalone, once developed and refined chatbots, intelligent agents, or complex workflows as plugins, making them seamlessly accessible to a 'master' or orchestrating agent. The 'master' agent can delegate different tasks to the appropriate "expert" based on the user's needs.

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

With this feature, I would be able to construct a highly modular and scalable system where multiple expert chatbots or agents, each focusing on specific tasks, or complex and complete workflows, can be deployed as needed. Developers could create and maintain task-specific chatbots, agents, or workflows independently, then easily plug them into more extensive systems, fostering a microservices-like approach to AI development. And developers can configure different 'expert' agents to a 'master' agent. This would not only enhance the capability of the master agent to handle a wide range of user requests efficiently but also pave the way for experimenting with multi-agent collaborative scenarios. BTW, I find that this is a bit like how Coze uses workflow some how.

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 @sunxichen on GitHub (May 16, 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 submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [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? Yes, currently, Dify allows only functions (built-in or custom) to be used as tools (plugins) for the large language model. However, I face a limitation where I cannot integrate pre-built chatbots, agents, or orchestrated workflows as tools. This missing capability hinders the full potential of creating modular and collaborative Agent solutions, especially in scenarios where multi-agent cooperation is paramount. ### 2. Describe the feature you'd like to see I would like to request an enhancement to Dify that extends the existing 'Tools' architecture to accommodate not just functions but also chatbots, agents, and workflows. The vision is to enable users to package their standalone, once developed and refined chatbots, intelligent agents, or complex workflows as plugins, making them seamlessly accessible to a 'master' or orchestrating agent. The 'master' agent can delegate different tasks to the appropriate "expert" based on the user's needs. ### 3. How will this feature improve your workflow or experience? With this feature, I would be able to construct a highly modular and scalable system where multiple expert chatbots or agents, each focusing on specific tasks, or complex and complete workflows, can be deployed as needed. Developers could create and maintain task-specific chatbots, agents, or workflows independently, then easily plug them into more extensive systems, fostering a microservices-like approach to AI development. And developers can configure different 'expert' agents to a 'master' agent. This would not only enhance the capability of the master agent to handle a wide range of user requests efficiently but also pave the way for experimenting with multi-agent collaborative scenarios. BTW, I find that this is a bit like how Coze uses workflow some how. ### 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🤖 feat:agent🌊 feat:workflow labels 2026-02-21 17:57:26 -05:00
yindo closed this issue 2026-02-21 17:57:26 -05:00
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 🌊 feat:workflow 💪 enhancement 🤖 feat:agent
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#3408
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?