Developing plugins¶
The plugin developer reference — manifest format, the full PluginAPI surface, permissions, and publishing — lives alongside the registry itself.
What you'll find there¶
- Quickstart — minimum viable plugin structure (
manifest.json+index.js) PluginAPIreference — connections, keys, identities, vault, storage, omni, ui, themes, sessions, lifecycle, http, fs, notifications, sync, events, plugins, log- Permissions table — every capability your manifest can request
- Worked examples — SSH config importer, theme plugin, Docker side panel
- Publishing — releasing on GitHub and submitting to
plugins.json
Why it lives in the marketplace repo¶
The reference ships next to the registry so the docs stay in lockstep with the published plugins.json schema and any breaking API changes are visible in the same PR.
Tip
For the user-facing side of plugins (installing, enabling, custom repos), see Installing plugins and Custom repos.