Guidance Needed: How to Support Tool, Model, and Endpoint Services Simultaneously in Latest Dify Plugin Version

[lpdink]

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.

Content

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 .difybndl extension in this repository.

I noticed that, as of the time of submitting this issue, the latest version of dify-plugin-daemon enforces 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 greatly appreciated!

[dosubot[bot]]

The latest dify-plugin-daemon enforces that a single plugin cannot serve as a model, tool, and endpoint at the same time, so splitting your solution into three separate plugins is required. Dify does support bundling multiple plugins together using the .difybndl format: the UI and backend recognize .difybndl files, trigger a bundle-specific installation flow, and the marketplace API has endpoints for bundles (e.g., /bundles/{org}/{name}/{version}) distinct from single plugins. This means the platform is technically ready for bundle uploads and installs, and the bundle mechanism is also used for offline/air-gapped environments where all dependencies must be included in the bundle file [source].

However, there is currently no official documentation or public example for creating or submitting .difybndl bundles to the marketplace, and community guidance suggests that for repository submissions, each plugin should be submitted individually, not as a bundle. For offline installs, you can pre-download all required .difypkg or .difybndl files and install them locally, but for marketplace publishing, the process for bundles is not clearly documented [source].

If you need to distribute a bundle for offline use, ensure your .difybndl is self-contained. For marketplace submission, you may need to submit each plugin separately until more guidance or tooling for bundles is provided. There are third-party tools (like dify-plugin-repackaging) that help with offline packaging, but these are not official solutions for marketplace bundles [source].

To reply, just mention @dosu.

---

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