mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-22 01:55:27 -04:00
[Guidance Needed]: How to Support Tool, Model, and Endpoint Services Simultaneously in Latest Dify Plugin Version #902
Reference in New Issue
Block a user
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?
Originally created by @lpdink on GitHub (Dec 25, 2025).
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Hi, I'm from the Alibaba Cloud ADBPG team and currently developing a Dify plugin.
I visited the Dify Plugin Marketplace but couldn't find any bundled plugin projects listed under the "Bundle" category. Additionally, I didn't locate any files with the
.difybndlextension in that repository.I noticed that, as of the time of submitting this issue, the latest version of
dify-plugin-daemonenforces a restriction preventing a single plugin from simultaneously serving as a model, tool, and endpoint (see this code line).In response to this limitation, I've refactored our original plugin into three separate plugins—one for each capability (tool, model, and endpoint)—and bundled them together. You can find our current implementation here: https://github.com/aliyun/alibabacloud-adbpg-dify-plugin.
What’s confusing is that I’m unable to provide tool, model, and endpoint capabilities within a single plugin, yet I also don’t understand how to properly publish or submit a bundle to the marketplace. Any guidance or suggestions would be appreciated!
2. Additional context or comments
No response
3. Can you help us with this feature?
@dosubot[bot] commented on GitHub (Dec 25, 2025):
Currently, Dify enforces a one-plugin-per-capability policy: you cannot combine tool, model, and endpoint services in a single plugin, so splitting them into separate plugins is required. Each plugin should be submitted individually to the marketplace—each folder is treated as a separate plugin, and submissions are reviewed one at a time. There is no official documentation or working example for bundling multiple plugins (such as with a
.difybndlfile) or publishing a bundle to the marketplace, even though the UI and backend have some bundle-related components and a "Bundle" category is visible in the interface. However, the workflow for submitting or publishing plugin bundles is not yet defined or supported in practice. For now, the best approach is to submit each capability as its own plugin and reference their relationship in your documentation or metadata if needed. This matches current repository and marketplace practices and aligns with recent guidance from maintainers and contributors.Source 1 | Source 2 | Source 3
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other