Skip to main content
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

version
required
Plugin version.
string
required
Plugin type. Currently only plugin is supported; bundle support is planned.
string
required
Author, defined as the organization name in the Marketplace.
object
required
Multilingual name.
RFC3339
required
Creation time. The Marketplace requires this to be no later than the current time.
string
required
Icon path.
object
Resources the plugin requests.
int64
Maximum memory usage in bytes. Mainly relates to AWS Lambda resource allocation on Dify Cloud.
object
Permissions the plugin requests.
object
Permission for reverse invocation of tools.
boolean
Whether to enable tool permissions.
object
Permission for reverse invocation of models.
boolean
Whether to enable model permissions.
boolean
Whether to enable large language model permissions.
boolean
Whether to enable text embedding model permissions.
boolean
Whether to enable rerank model permissions.
boolean
Whether to enable text-to-speech model permissions.
boolean
Whether to enable speech-to-text model permissions.
boolean
Whether to enable content moderation model permissions.
object
Permission for reverse invocation of nodes.
boolean
Whether to enable node permissions.
object
Permission to register endpoint.
boolean
Whether to enable endpoint permissions.
object
Permission for reverse invocation of app.
boolean
Whether to enable app permissions.
object
Permission to apply for persistent storage.
boolean
Whether to enable storage permissions.
int64
Maximum allowed persistent storage size, in bytes.
object
required
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.
array[string]
Plugin extension for Tool providers.
array[string]
Plugin extension for Model providers.
array[string]
Plugin extension for Endpoints providers.
array[string]
Plugin extension for Agent Strategy providers.
object
required
Metadata for the plugin.
version
required
Manifest format version. The initial version is 0.0.1.
array[string]
required
Supported architectures. Currently only amd64 and arm64 are supported.
object
required
Runtime configuration.
string
required
Programming language. Currently only Python is supported.
string
required
Language version. Currently only 3.12 is supported.
string
required
Program entry point. For Python, this should be main.
string
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.
Last modified on June 25, 2026