Plugins

Plugins extend FluffBuzz with new capabilities: channels, model providers, tools, skills, speech, image generation, and more. Some plugins are core (shipped with FluffBuzz), others are external (published on npm by the community).

Quick start

See what is loaded

fluffbuzz plugins list

Install a plugin

# From npm
fluffbuzz plugins install @fluffbuzz/voice-call

# From a local directory or archive
fluffbuzz plugins install ./my-plugin
fluffbuzz plugins install ./my-plugin.tgz

Restart the Gateway

fluffbuzz gateway restart

Then configure under plugins.entries.\<id\>.config in your config file.

If you prefer chat-native control, enable commands.plugins: true and use:

/plugin install buzzhub:@fluffbuzz/voice-call
/plugin show voice-call
/plugin enable voice-call

The install path uses the same resolver as the CLI: local path/archive, explicit buzzhub:<pkg>, or bare package spec (ClawHub first, then npm fallback).

Plugin types

FluffBuzz recognizes two plugin formats:

Format	How it works	Examples
Native	`fluffbuzz.plugin.json` + runtime module; executes in-process	Official plugins, community npm packages
Bundle	Codex/Claude/Cursor-compatible layout; mapped to FluffBuzz features	`.codex-plugin/`, `.claude-plugin/`, `.cursor-plugin/`

Both show up under fluffbuzz plugins list. See Plugin Bundles for bundle details. If you are writing a native plugin, start with Building Plugins and the Plugin SDK Overview.

Official plugins

Installable (npm)

Plugin	Package	Docs
Matrix	`@fluffbuzz/matrix`	Matrix
Microsoft Teams	`@fluffbuzz/msteams`	Microsoft Teams
Nostr	`@fluffbuzz/nostr`	Nostr
Voice Call	`@fluffbuzz/voice-call`	Voice Call
Zalo	`@fluffbuzz/zalo`	Zalo
Zalo Personal	`@fluffbuzz/zalouser`	Zalo Personal

Core (shipped with FluffBuzz)

Model providers (enabled by default)

anthropic, byteplus, cloudflare-ai-gateway, github-copilot, google, huggingface, kilocode, kimi-coding, minimax, mistral, modelstudio, moonshot, nvidia, openai, opencode, opencode-go, openrouter, qianfan, qwen-portal-auth, synthetic, together, venice, vercel-ai-gateway, volcengine, xiaomi, zai

Memory plugins

memory-core — bundled memory search (default via plugins.slots.memory)
memory-lancedb — install-on-demand long-term memory with auto-recall/capture (set plugins.slots.memory = "memory-lancedb")

Speech providers (enabled by default)

elevenlabs, microsoft

Other

copilot-proxy — VS Code Copilot Proxy bridge (disabled by default)

Looking for third-party plugins? See Community Plugins.

Configuration

{
  plugins: {
    enabled: true,
    allow: ["voice-call"],
    deny: ["untrusted-plugin"],
    load: { paths: ["~/Projects/oss/voice-call-extension"] },
    entries: {
      "voice-call": { enabled: true, config: { provider: "twilio" } },
    },
  },
}

Field	Description
`enabled`	Master toggle (default: `true`)
`allow`	Plugin allowlist (optional)
`deny`	Plugin denylist (optional; deny wins)
`load.paths`	Extra plugin files/directories
`slots`	Exclusive slot selectors (e.g. `memory`, `contextEngine`)
`entries.\<id\>`	Per-plugin toggles + config

Config changes require a gateway restart. If the Gateway is running with config watch + in-process restart enabled (the default fluffbuzz gateway path), that restart is usually performed automatically a moment after the config write lands.

Plugin states: disabled vs missing vs invalid

Disabled: plugin exists but enablement rules turned it off. Config is preserved.
Missing: config references a plugin id that discovery did not find.
Invalid: plugin exists but its config does not match the declared schema.

Discovery and precedence

FluffBuzz scans for plugins in this order (first match wins):

Config paths

plugins.load.paths — explicit file or directory paths.

Workspace extensions

\<workspace\>/.fluffbuzz/extensions/*.ts and \<workspace\>/.fluffbuzz/extensions/*/index.ts.

Global extensions

~/.fluffbuzz/extensions/*.ts and ~/.fluffbuzz/extensions/*/index.ts.

Bundled plugins

Shipped with FluffBuzz. Many are enabled by default (model providers, speech). Others require explicit enablement.

Enablement rules

plugins.enabled: false disables all plugins
plugins.deny always wins over allow
plugins.entries.\<id\>.enabled: false disables that plugin
Workspace-origin plugins are disabled by default (must be explicitly enabled)
Bundled plugins follow the built-in default-on set unless overridden
Exclusive slots can force-enable the selected plugin for that slot

Plugin slots (exclusive categories)

Some categories are exclusive (only one active at a time):

{
  plugins: {
    slots: {
      memory: "memory-core", // or "none" to disable
      contextEngine: "legacy", // or a plugin id
    },
  },
}

Slot	What it controls	Default
`memory`	Active memory plugin	`memory-core`
`contextEngine`	Active context engine	`legacy` (built-in)

CLI reference

fluffbuzz plugins list                    # compact inventory
fluffbuzz plugins inspect <id>            # deep detail
fluffbuzz plugins inspect <id> --json     # machine-readable
fluffbuzz plugins status                  # operational summary
fluffbuzz plugins doctor                  # diagnostics

fluffbuzz plugins install <package>        # install (ClawHub first, then npm)
fluffbuzz plugins install buzzhub:<pkg>   # install from ClawHub only
fluffbuzz plugins install <path>          # install from local path
fluffbuzz plugins install -l <path>       # link (no copy) for dev
fluffbuzz plugins update <id>             # update one plugin
fluffbuzz plugins update --all            # update all

fluffbuzz plugins enable <id>
fluffbuzz plugins disable <id>

See fluffbuzz plugins CLI reference for full details.

Plugin API overview

Plugins export either a function or an object with register(api):

export default definePluginEntry({
  id: "my-plugin",
  name: "My Plugin",
  register(api) {
    api.registerProvider({
      /* ... */
    });
    api.registerTool({
      /* ... */
    });
    api.registerChannel({
      /* ... */
    });
  },
});

Common registration methods:

Method	What it registers
`registerProvider`	Model provider (LLM)
`registerChannel`	Chat channel
`registerTool`	Agent tool
`registerHook` / `on(...)`	Lifecycle hooks
`registerSpeechProvider`	Text-to-speech / STT
`registerMediaUnderstandingProvider`	Image/audio analysis
`registerImageGenerationProvider`	Image generation
`registerWebSearchProvider`	Web search
`registerHttpRoute`	HTTP endpoint
`registerCommand` / `registerCli`	CLI commands
`registerContextEngine`	Context engine
`registerService`	Background service

Building Plugins — create your own plugin
Plugin Bundles — Codex/Claude/Cursor bundle compatibility
Plugin Manifest — manifest schema
Registering Tools — add agent tools in a plugin
Plugin Internals — capability model and load pipeline
Community Plugins — third-party listings

Overview

Plugins

Skills

Automation

Tools

Agent coordination

Plugins

Plugins

Quick start

Plugin types

Official plugins

Installable (npm)

Core (shipped with FluffBuzz)

Configuration

Discovery and precedence

Enablement rules

Plugin slots (exclusive categories)

CLI reference

Plugin API overview

Overview

Plugins

Skills

Automation

Tools

Agent coordination

​Plugins

​Quick start

​Plugin types

​Official plugins

​Installable (npm)

​Core (shipped with FluffBuzz)

​Configuration

​Discovery and precedence

​Enablement rules

​Plugin slots (exclusive categories)

​CLI reference

​Plugin API overview

​Related

Plugins

Quick start

Plugin types

Official plugins

Installable (npm)

Core (shipped with FluffBuzz)

Configuration

Discovery and precedence

Enablement rules

Plugin slots (exclusive categories)

CLI reference

Plugin API overview

Related