Code Example
Below is a simple example of a Manifest file. The meaning and function of each data item will be explained later. For reference code of other plugins, please refer to the GitHub code repository.Structure
The version of the plugin.
Plugin type, currently only
plugin is supported, bundle will be supported in the future.Author, defined as the organization name in the Marketplace.
Multilingual name.
Creation time, required by the Marketplace not to be later than the current time.
Icon path.
Resources to apply for.
Maximum memory usage, mainly related to AWS Lambda resource application on SaaS, unit in bytes.
Permission application.
Permission for reverse invocation of tools.
Whether to enable tool permissions.
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.
Permission for reverse invocation of nodes.
Whether to enable node permissions.
Permission to register
endpoint.Whether to enable endpoint permissions.
Permission for reverse invocation of
app.Whether to enable app permissions.
A list of
yaml files for the specific capabilities extended by the plugin. Absolute path within the plugin package. For example, if you need to extend a model, you need to define a file similar to openai.yaml, fill in the file path here, and the file at this path must actually exist, otherwise packaging will fail.Plugin extension for Agent Strategy providers.
Metadata for the plugin.
manifest format version, initial version 0.0.1.Supported architectures, currently only
amd64 and arm64 are supported.Specifies the relative path or URL of the plugin’s privacy policy file, e.g.,
"./privacy.md" or "https://your-web/privacy". If you plan to list the plugin on the Dify Marketplace, this field is required to provide clear user data usage and privacy statements. For detailed filling guidelines, please refer to Plugin Privacy Data Protection Guidelines.Edit this page | Report an issue