Skip to main content

​
Plugins

Plugins extend the Gateway with trusted code. They can add channel runtimes, model-provider auth flows, Agent tools, slash commands, skills, hooks, and Gateway RPC methods. Use plugins when a feature needs runtime code that is not part of the core Gateway. Use Agent > Skills when you only need instructions. Use Agent > Services when you only need credentials for an existing service.

​
Where Plugin Setup Lives

  • Install, enable, disable, update, inspect: Extensions or fased plugins ....
  • Channel account setup: Agent > Channels.
  • Agent tool allow/deny: Agent > Tools.
  • Skill access and dependency setup: Agent > Skills.
  • Provider sign-in/API key: Agent > Models.
  • Raw plugin config: Advanced > Config when no focused UI exists.
Plugins are runtime extensions. They do not automatically grant a selected Agent permission to use every tool, skill, channel, or wallet-related path they expose.

​
Install And Enable

List plugins:
Install one of the published official channel add-ons:
Install from a local checkout:
Enable or disable:
Restart the Gateway after changing runtime plugin state.

​
What A Plugin Can Provide

  • Channel runtime, such as Zalo Personal or external chat adapters. Setup surface: Agent > Channels.
  • Agent tool, such as a workflow helper or voice-call tool. Setup surface: Agent > Tools.
  • Skill pack, such as plugin-owned skills/<name>/SKILL.md. Setup surface: Agent > Skills.
  • Provider auth, such as OAuth or token setup for a model provider. Setup surface: Agent > Models.
  • Gateway method, such as pluginId.status or pluginId.action. Setup surface: plugin-specific docs or CLI.
  • Slash command, such as /plugin-command ... without a model turn. Setup surface: chat/channel command surface.
  • Hook, such as a lifecycle/event hook registered by the plugin. Setup surface: plugin lifecycle, not Hooks UI.
Channel plugins put account config under channels.<id>, not plugins.entries.<id>.config, because Channels owns account setup and routing. Agent tools registered by plugins still require Agent tool policy. Skills shipped by plugins still require Agent skill access. Wallet, mining, marketplace, and node actions keep their own approval gates.

​
Manifest Requirement

Every plugin must ship fased.plugin.json in the plugin root. The manifest lets Fased validate plugin config without executing plugin code. Minimal manifest:
Read the full reference in Plugin manifest.

​
Bundled Advanced Examples

Voice Call, Zalo Personal, ACPX, and the other advanced extensions in the repository are source-maintained bundled extensions in this release. They are not part of the public npm add-on set. Enable the bundled copy or use a local source checkout; do not assume an @fased/* package is published because its source directory has a package manifest.

OpenProse

Markdown-first workflow programs and an optional skill pack.

Voice Call

Bundled outbound and inbound call workflows through a trusted plugin.

Zalo Personal

Personal Zalo channel runtime backed by the bundled extension.

Community Plugins

Listing requirements and third-party plugin quality bar.

​
Safety

Plugins run in the Gateway process. Treat them as trusted code.
  • Install plugins only from sources you trust.
  • Prefer plugins.allow allowlists for non-bundled plugins.
  • Keep plugin dependency installs pinned and reviewed.
  • Do not use a plugin to bypass Agent tool policy, wallet approvals, mining controls, marketplace authority, or channel access policy.
  • Missing or invalid manifests should block config validation.

​
Developer References