Plugin development

Kumbuka extensions are implemented as versioned plugins. The public plugin contract lives in kumbuka-me/sdk, while first-party implementations and releases live in kumbuka-me/plugins.

Use declarative manifest modules where possible. Executable server-side behavior runs as WASI, browser modules render inside isolated frames, and Kumbuka remains responsible for authorization, capability enforcement, sanitization, and lifecycle management.

• Getting started — create, test, build, and install a plugin.
• SDK — public Go packages and helpers.
• Manifest and modules — package metadata and contribution types.
• Capabilities — host operations available to executable plugins.
• Browser modules — isolated client-side rendering.
• Package format — .kumbukaplugin archive structure and limits.
• Wire protocol — low-level WASI ABI for implementations that do not use the Go SDK.

Browse Extensions for first-party plugin usage documentation. Installation and lifecycle administration are documented under Administration → Plugins.