Plugins, marketplace, connections & secrets

This page covers four related Web UI screens that extend the instance and hold credentials: Plugins/Marketplace, Connections and Secrets.

Install a plugin in 4 steps

Plugins are channel connectors, services, integrations and skills. Installing is a single click:

Open the “Plugins” screen and go to the “Catalog/store” block.
Find the plugin you want (there is search and filters by kind and state). Official modules carry an Official badge and come first.
Click “Install”. What you’ll see: the card shows a progress bar and refreshes itself until the plugin turns “online”.
Click “Configure” — a form built from the plugin manifest opens (e.g. a token field for a channel connector). Fill it in and save.

What’s next: after install a channel connector appears on the Channels screen, and an integration/connection on the “Connections” screen. Until installed, a plugin does not appear on those screens.

[!NOTE] Community plugins. Besides the official catalog, you can add third-party (community) sources in the “Sources” block: enter a catalog name and URL, enable it and sync. Plugins from such sources are verified against the instance trust-store — on first load the operator approves the author’s key. Details: Install & updates.

Plugins / Marketplace

The “Plugins” screen is the single install surface for all modules: channel connectors, services, OpenAPI integrations, skills and MCP are installed only here. Until a plugin is installed it does not appear on the “Channels” and “Connections” screens; once installed, its configuration shows up there.

Installed (shown first) — cards with logo, name, a kind badge and a status (online / error / deploying / blocked). Actions: Configure (a form built from the plugin manifest), Update to latest (when the catalog has a newer version), Uninstall (with confirmation; except built-ins). Modules with no visible settings fields — Einstein, for one — have no Configure button at all; only the update action is available. Banners may appear for “needs a public URL” and “not available on your plan”. The Einstein memory plugin is built-in: it is listed among the installed modules with a “Built-in” badge, never offered in the store and cannot be uninstalled.
Catalog/store — the full catalog, channel connectors included: official modules first, the rest sorted by installs. There is a search box and filters by kind (connector / service / integration / skill / MCP) and state (installed / not installed). A module not available on the current plan stays visible — instead of “Install” it shows an “Upgrade to unlock” link (the server answers HTTP 402, see Licensing).
During install/update the card shows a progress bar and the screen refreshes itself every few seconds until it settles.
Sources — the official source is pinned; private sources can be added (name + URL), enabled/disabled, removed and synced.

Details in Marketplace & plugins.

Connections (OAuth, multi-account)

The “Connections” screen is a personal store of external-service credentials.

My connections — service logo, format, label, status; a disconnect button.
Available — catalog entries scoped “personal”: OAuth services start authorization via redirect (on first use they ask for client_id/secret, which go into the vault); token services show manifest-declared fields (for example e-mail and token) and are saved as credentials.
+ account — multi-account: each label is a separate connection of the same service.
A Devices block — the status of iOS device bridges.

Secrets (vault)

The “Secrets” screen is a write-only store: secret values are never read back. “+ New secret” is a modal with fields: scope, name, value (password). The list shows scope, name and a “set” badge plus delete. Secrets are used by plugins and agents without ever being revealed in the UI.

If it didn’t work

An “Upgrade to unlock” link instead of “Install” — the module isn’t available on your current plan (the server answers HTTP 402). Change plan or pick another module, see Licensing.
The card is stuck installing/errored — an install counts as successful only after the plugin’s health check; a broken plugin is not counted. Try reinstalling, details in Install & updates.
The plugin isn’t in the catalog — check the filters (kind/state) and search; for a third-party plugin, add and sync its source in the “Sources” block.
Can’t find an installed plugin’s settings — they appear after install: for channels on the Channels screen, for connections on “Connections”.

Install & updates — plugin lifecycle.
Connections & OAuth — multi-account.
Vault — how secrets are stored.