Skip to main content

Plugin development guide

This section is for ecosystem developers. It covers the architecture of the Qomicex plugin system (plugin system), the development workflow, and every interface.

What a plugin is

A Qomicex plugin (Plugins)(.qplugin) is essentially a ZIP archive containing a manifest.json manifest and the plugin’s frontend assets (HTML / JS / CSS). After installation the Launcher (Launcher)renders and executes it in a controlled sandbox or inline environment, where it can call the plugin API (plugin API)exposed by the launcher to read and write settings, operate on instances, make network requests, and inject UI.

Plugin capabilities

Library plugins (Library plugin)

Some plugins provide no UI and exist only as capability libraries that other plugins depend on (for example, MarkdownLib provides renderMarkdown). These plugins declare no contributes, so they create no sidebar entry. See Plugin dependencies and inter-plugin calls.

Contents (contents)

Getting started Core reference Advanced Tooling and debugging Publishing and quality