E
Docs/Customization/Plugins

Plugins

Planned bundles for skills, connectors, and local developer capabilities.

Draft

Plugin Model#

Plugins are intended to group related capabilities into an installable unit. A plugin may include skills, tool servers, connectors, or local configuration, but each capability should keep its own permission boundary.

Lifecycle#

  • Discover: Inspect source, publisher, required applications, and permissions.
  • Install: Add the plugin to a local or account-scoped catalog.
  • Update: Review capability and permission changes before accepting an update.
  • Remove: Uninstall the plugin and clean up its local registration without deleting user data by surprise.

Manifest#

Conceptual shape
{
  "name": "example-plugin",
  "version": "0.0.0",
  "capabilities": ["skills", "tools"]
}

Registry Status#

Distribution not available

No official public registry, signing policy, or compatibility matrix is documented yet.