Skip to content

Plugin / Extension System #21

@antiv

Description

@antiv

Summary

Formalized plugin architecture: drop a Python package into plugins/ and it auto-registers tools, agent types, dashboard pages, and API endpoints. Plugin manifest with versioning.

Motivation

MATE has ToolFactory and custom tools but no formal plugin system. A plugin architecture makes community contribution easier without forking core, and lets enterprises add proprietary integrations cleanly.

Scope

  • Plugin directory (plugins/) scanned on startup
  • Plugin manifest (plugin.yaml): name, version, dependencies, entry points
  • Plugin API surface: register tools, register agent types, register dashboard routes, register API endpoints
  • Plugin manager in dashboard: list installed, enable/disable, view logs
  • Plugin isolation: plugins can't modify core tables without migration
  • Example plugin: "Hello World" tool + dashboard page

Acceptance Criteria

  • Plugins auto-discovered from plugins/ directory
  • Plugin can register custom tools visible in ToolFactory
  • Plugin can add dashboard pages
  • Dashboard plugin manager lists and toggles plugins
  • Example plugin included

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Medium priorityarchitectureCore architectureenhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions