langgenius/dify-plugins

Dify Cloud · Self-hosting · Documentation · Enterprise inquiry

Introducing Dify Plugins

Dify is an open-source platform for developing LLM-powered AI applications, designed to help developers and businesses efficiently build, deploy, and manage AI-driven solutions. With Dify, users can easily create and test complex AI workflows, integrate a wide range of advanced models and tools, and optimize their performance in real-world applications. The platform offers an intuitive interface, supporting RAG (Retrieval-Augmented Generation) pipelines, intelligent agent capabilities, and robust model management, enabling developers to seamlessly transition from prototype to production.

Dify Marketplace is a vibrant center that allows developers, businesses, and AI enthusiasts to explore, share, and deploy plugins designed to enhance Dify Apps' capabilities. It serves as a platform where users can discover a wide range of models, tools, agent strategies, extensions, and bundles, all of which can be seamlessly integrated into their AI applications. By providing a collaborative space for both official and community-contributed plugins, the Dify Marketplace encourages innovation and resource sharing.

Plugin Development

Types of Plugin

Models

These plugins integrate various AI models, including mainstream LLM providers and custom models, to handle configuration and requests for model APIs. For more on creating a model plugin, refer to the Dify Plugin documentation.

Tools

Tools are third-party services that can be invoked by Chatflow, Workflow, or Agent applications. They provide API-backed capabilities for Dify applications. For plugin type guidance, refer to Choose a Plugin Type.

Agent Strategies

The Agent Strategy plugin defines the reasoning and decision-making logic within an Agent node, including tool selection, invocation, and result processing.

Agent strategy plugins define the internal reasoning and decision-making logic within agent nodes. They encompass the logic for tool selection, invocation, and handling of returned results by the LLM. For further development guidance, please refer to the Quick Start: Agent Strategy Plugin.

Extensions

Lightweight plugins that only provide endpoint capabilities for simpler scenarios, enabling fast expansions via HTTP services. This approach is ideal for straightforward integrations requiring basic API invoking. For more details, refer to Quick Start: Extension Plugin.

Bundles

A "plugin bundle" is a collection of multiple plugins. Bundles allow you to install a curated set of plugins all at once—no more adding them one by one. For more information on creating plugin bundles, see Plugin Development: Bundle Plugin.

Plugin Docs

Check the Plugins documentation to learn how to develop and publish plugins.

Publishing to Dify Marketplace

To publish your plugin on the Dify Marketplace, follow these steps:

Development

1. Develop and test your plugin according to the Plugin Development Guidelines and this repository's Plugin Submission Requirements.

2. Write a Plugin Privacy Policy for your plugin in line with Dify's privacy requirements. In your plugin's manifest, include the file path or URL for this privacy policy.

3. Include your contact information and source repository URL in the plugin README.md.

Publishing

1. Package your plugin into .difypkg file for distribution.

2. Fork this repository.

3. Create an organization directory under the repository's main structure, then create a subdirectory named after your plugin. Place your plugin source code and the packaged .difypkg file in that subdirectory, for example langgenius/dify-plugin/dify-plugin-0.0.1.difypkg. You can place different versions in the same subdirectory.

4. Submit a Pull Request (PR) following the required PR template format, then wait for review.

5. Once approved, your plugin code will merge into the main branch, and the plugin will be automatically listed on the Dify Marketplace.

Updating/Bump

1. When updating your plugin, increment the version in your plugin's manifest.yaml file.

2. Each PR for plugin updates must contain only one file change - the new .difypkg file. Check that the version hasn't been published before.

3. If your update includes breaking changes, document them clearly in your plugin's README.md to prevent user issues.

4. For faster plugin updates, you can set up automated PR workflows using the Plugin Auto-PR guide. This automates packaging and PR creation when you release new versions.

Security disclosure

To protect your privacy, please avoid posting security issues on GitHub. Instead, send your questions to [email protected] and we will provide you with a more detailed answer.