Skip to Content
Addon DevelopmentIntroduction

Introduction to M2C2 addons

An addon is a self-contained package dropped into the M2C2 addons/ directory (exact path depends on install). Each addon ships:

  • manifest.json — identity, permissions, entrypoints.
  • UI bundle — React components rendered inside AddonWidget sandboxes.
  • Optional server routes — registered under /api/addons/:addonId/* when allowed.
  • Optional Python service — long-running workers for CV / ML / device bridges.

💡 Tip: Keep addons single-purpose — “crypto price tile” and “quote of the day” are easier to test than a mega-addon that touches ten permissions.

Lifecycle

  1. Discovery — core scans addons/*/manifest.json at startup.
  2. Activation — user enables addon in Settings → Addons.
  3. Render — dashboard mounts your widget with injected context (theme, locale, settings).
  4. Updates — marketplace delivers semver bundles; core migrates stored settings when manifest.migrations runs.

⚠️ Warning: Addons run with whatever permissions you declare. Request least privilege — reviewers and users reject overbroad * scopes.

Next

Read Addon file structure.

Last updated on
Addon file structure

Was this helpful?