AiHummer
English▾
Log in
v1.0.x▾
v1.0.xstable
{ }Swagger
Web UI/Plugins, marketplace, connections & secrets

Plugins, marketplace, connections & secrets

v1.0.x · updated 2026-07-10

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

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). 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.

More in Connections & OAuth.

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.

Next