Overview
ThePluginDefinition type defines the core configuration for an Atomemo plugin. It contains metadata, localization settings, and optional transporter configuration.
Importing Types
Types are re-exported from the SDK and can be imported from the types entry point:Type Definition
Properties
The unique identifier for the plugin. Must be a valid plugin name.Example:
"my-plugin"Localized display names for the plugin. Keys should match the locales defined in the
locales property.Example:Localized descriptions of what the plugin does. Keys should match the locales defined in the
locales property.Example:An emoji or icon representation of the plugin.Example:
"π" or "β‘"The name of the plugin author. This is automatically populated from the user session in debug mode or from
definition.json in release mode.Note: You typically donβt need to provide this manually.The email address of the plugin author. This is automatically populated from the user session in debug mode or from
definition.json in release mode.Note: You typically donβt need to provide this manually.The semantic version of the plugin. Defaults to
process.env.npm_package_version if not provided.Example: "1.0.0"An array of supported locale codes. These locales determine which keys are valid in
display_name and description.Example: ["en_US", "es_ES", "fr_FR"]Optional configuration for the network transporter that connects to the Hub Server. See TransporterOptions for details.
Example
Related Types
- TransporterOptions - Configuration for the network transporter
- CredentialDefinition - For adding credentials to the plugin
- ToolDefinition - For adding tools to the plugin
- ModelDefinition - For adding models to the plugin
See Also
- createPlugin() - Function that accepts this type
- Creating a Plugin - Step-by-step guide