Skip to main content

​
fased plugins

Manage gateway plugins and extensions that load in-process with the runtime. Related:

​
Commands

Bundled plugins ship with Fased but start disabled unless a setup path enables them. Telegram, WhatsApp, Discord, Slack, Feishu, and Google Chat are official add-ons rather than bundled core plugins:

​
Runtime helper grants

Plugins do not receive runtime helper access by default. Grant read-only, sanitized session metadata access explicitly:
This toggles plugins.entries.<id>.runtime.helpers.sessions.read. It does not enable the plugin itself. Restart the gateway after changing the grant so the active plugin runtime reloads with the new permission.

​
Install

Rules:
  • plugin packages must include fased.plugin.json
  • the manifest must include a valid inline schema
  • npm specs are registry-only
  • Git and arbitrary remote specs are rejected
  • dependency install uses --ignore-scripts
Supported local archives:
  • .zip
  • .tgz
  • .tar.gz
  • .tar
--link adds a local directory to plugins.load.paths instead of copying it. --pin stores the exact resolved npm version in plugins.installs.

​
Uninstall

Normal uninstall removes:
  • plugins.entries
  • plugins.installs
  • plugin allowlist references
  • linked load paths when applicable
By default it also removes the installed plugin directory under:
  • $FASED_STATE_DIR/extensions/<id>
--keep-files leaves those files on disk. --keep-config is a deprecated alias for --keep-files. --force skips the uninstall confirmation prompt.

​
Update

Updates apply to npm-installed plugins tracked in plugins.installs. If a stored integrity hash exists and the fetched artifact no longer matches, Fased warns before proceeding. Use --approve-risky-changes only after reviewing source, dependency/script, or permission-surface changes.