plugin

[zhouji1026]

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

/dify/docker/volumes/plugin_daemon/plugin/
/dify/docker/volumes/plugin_daemon/plugin_packages/
May I ask what the difference is between these two catalogs?

[dosubot[bot]]

These two directories serve different purposes in the plugin installation workflow:

• plugin/ — Stores installed and active plugins that are ready to be executed by the plugin daemon. This is where plugins live once they're fully set up and running. (Configured via PLUGIN_INSTALLED_PATH) [1]

• plugin_packages/ — Acts as a cache for plugin packages during the installation process. When you install a plugin, the package file is first stored here before being extracted and moved to the plugin/ directory. (Configured via PLUGIN_PACKAGE_CACHE_PATH) [1]

In short, the workflow is: packages are uploaded/downloaded to plugin_packages/ (staging area), then installed/extracted into plugin/ where they become active [2].

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.