Skip to main content

Plugin gallery

Open Plugins to see installed extensions, including disabled ones. Cards show the manifest label, description, cover, kind and declared surfaces. A disabled plugin retains its card so it can be enabled again.

The @timon family identifies product-authored plugins. Third-party packages appear in the Marketplace family; a verified badge describes signature verification, not the plugin's purpose or whether it is enabled. This view is a local installed catalogue, not a promise of a remote store.

Enable or disable​

Use the card's toggle or the CLI with the manifest ID:

timon plugin list
timon plugin disable acme-example
timon plugin enable acme-example

Toggles update the desired configuration and the loader reconciles the plugin without restarting the daemon. Installing or enabling third-party code through the UI requires a superadmin account.

A refused plugin displays its reason. An incompatible contract, invalid signature or missing licence cannot be repaired by toggling repeatedly. Core modules needed for the daemon have no usable off switch.

Install a supplied package​

timon plugin add ./my-plugin

Inspect its requested permissions and approve only code you trust. Host plugins run inside the daemon process. See Testing and installation for signature and developer-mode requirements.

Removing a widget from a layout is different from disabling its plugin: the widget palette can restore a removed card, while an unavailable plugin cannot render it. Themes must also be selected in Appearance before their palette is used.

Mail Sentinel​

The Mails tile is an optional third-party plugin and is no longer built in or preinstalled. Install the supplied package by path:

timon plugin add ./plugins/mail-sentinel

This relative path is for a source checkout; otherwise use the path where you received the package. Signature and developer-mode requirements still apply. The separate Mail Sentinel service must already be running.

Your previously saved service URL is carried over automatically, even if you install the plugin later. An existing serviceUrl setting is never overwritten. If you configured the old integration only through an environment variable, enter the URL in Settings → Mail Sentinel → serviceUrl.

Add the service hostname, without scheme or port, to pluginPolicy.http.allow in your Timon configuration. For example, a service at http://127.0.0.1:8090 needs 127.0.0.1 in that list. Keep your other allowed hosts. Migration never changes this allowlist automatically.

The new widget uses its default placement; the old Mails placement is ignored. Only grant plugin access to users allowed to read the configured mailboxes.