The manifest is a YAML file that defines a plugin’s basic information: name, author, included tools and models, and more. If the file is malformed, plugin parsing and packaging fails.
For the overall plugin architecture, see Basic Concepts of Plugin Development and the Developer Cheatsheet.
Code Example#
Below is a simple manifest file; each field is explained in the Structure section that follows. For a real-world example, see the Google tool plugin manifest.
Structure#
Plugin version.
Plugin type. Currently only plugin is supported; bundle support is planned.
Multilingual name.
Creation time. The Marketplace requires this to be no later than the current time.
Icon path.
Resources the plugin requests.
Maximum memory usage in bytes. Mainly relates to AWS Lambda resource allocation on Dify Cloud.
Permissions the plugin requests.
Permission for reverse invocation of models.
Whether to enable model permissions.
Whether to enable large language model permissions.
Whether to enable text embedding model permissions.
Whether to enable rerank model permissions.
Whether to enable text-to-speech model permissions.
Whether to enable speech-to-text model permissions.
Whether to enable content moderation model permissions.
Lists the YAML files for the capabilities the plugin extends, as absolute paths within the plugin package. For example, to extend a model, define a file such as openai.yaml and list its path here. The file must exist at that path, or packaging fails.
The following combinations are not allowed:
- Extending both tools and models.
- Extending both models and Endpoints.
- Having no extensions at all.
Currently, each extension type supports only one provider.
Plugin extension for Agent Strategy providers.
Metadata for the plugin.
Manifest format version. The initial version is 0.0.1.
Supported architectures. Currently only amd64 and arm64 are supported.
Relative path or URL of the plugin’s privacy policy, for example "./privacy.md" or "https://your-web/privacy". Required for listing on the Dify Marketplace, where plugins must clearly state how they use user data. For details, see the Plugin Privacy Data Protection Guidelines.