.so plugins. The otter-shell metapackage installs the examples (otter-shell-plugins) and the scaffold CLI (otter-plugin-factory).
A loaded plugin is native code inside the bar or launcher. Only enable plugins you installed and trust.
Enable a plugin
Open otter-settings and go to the Plugins tab. Each installed plugin has a toggle. That writes~/.config/otter-shell/plugins.conf:
snippet-provider is opt-in and stays off until you set snippet-provider_enabled = true.
Put it on the bar
Layout names always useplugin:<id>. The id is the id field in plugin.conf, not the package name.
In otter-settings, drag an enabled plugin chip into the bar layout. Or edit otter-bar.conf:
Example plugins
These land under/usr/lib/otter-shell/plugins/<id>/ with otter-shell-plugins:
plugin:bluetooth-applet comes from the otter-bluetooth-plugin package, which otter-shell-plugins depends on. A normal plugins install includes it under /usr/lib/otter-shell/plugins/bluetooth-applet/.
Install path
Hosts look for plugins in this order. First match per id wins:OTTER_PLUGIN_PATH(colon-separated roots)$XDG_DATA_HOME/otter-shell/plugins~/.local/share/otter-shell/plugins/usr/lib/otter-shell/plugins/usr/share/otter-shell/plugins
plugin.conf and the matching .so.
To try a local build without installing:

