Plugins

Public preview: the Plugin API v1 manifest, bundle verification and declarative-contribution contracts are available for review and template development. The SDK is published as @gordo-labs/tape-plugins-sdk (opens in a new tab) and maintained in its public GitHub repository (opens in a new tab). Automatic installation, a marketplace and executable community-plugin code are not released capabilities.

Plugins extend Music Hub without receiving unrestricted access to Desktop or a user's library. The host owns privileged work and grants a small, versioned capability surface instead. This makes a core add-on such as Music Hub Network and an independently versioned community package follow the same boundary.

Internal testing

Plugin previews, tester builds and feedback are coordinated through the Music Hub Telegram groups:

• Public Music Hub group (opens in a new tab)

What is available in this preview

• Plugin API version 1 manifest validation and host compatibility checks.
• @gordo-labs/tape-plugins-sdk, a runtime-independent manifest SDK available from GitHub (opens in a new tab) for independent repositories.
• A community-plugin template with a JSON bundle, SHA-256 artifact integrity declaration and optional Ed25519 publisher signature.
• Permission-filtered declarative workspaces, context actions, settings and enrichment-provider contributions.
• A data-only community runtime that reads a bounded, hashed JSON descriptor; it does not load, import, evaluate or execute the bundle artifact.

Trust tiers

• Core: ships with Music Hub and is reviewed with the app release.
• Official: signed and distributed by Music Hub.
• Verified: reviewed third-party package with explicit capability grants.
• Community: publisher-signed, sideloaded bundle subject to the community permission allowlist and declarative runtime.
• Local development: unpacked development build, visibly unsafe and never a substitute for package verification.

No third-party tier receives Electron, Node, shell, filesystem, database, pairing, mobile-session, service-credential or raw /api/* access. Start with Getting Started, then read the manifest, permissions and distribution contracts.