@tencent-weixin/fluffbuzz-weixin channel plugin.
Status: external plugin. Direct chats and media are supported. Group chats are not
advertised by the current plugin capability metadata.
Naming
- WeChat is the user-facing name in these docs.
- Weixin is the name used by Tencent’s package and by the plugin id.
fluffbuzz-weixinis the FluffBuzz channel id.@tencent-weixin/fluffbuzz-weixinis the npm package.
fluffbuzz-weixin in CLI commands and config paths.
How it works
The WeChat code does not live in the FluffBuzz core repo. FluffBuzz provides the generic channel plugin contract, and the external plugin provides the WeChat-specific runtime:fluffbuzz plugins installinstalls@tencent-weixin/fluffbuzz-weixin.- The Gateway discovers the plugin manifest and loads the plugin entrypoint.
- The plugin registers channel id
fluffbuzz-weixin. fluffbuzz channels login --channel fluffbuzz-weixinstarts QR login.- The plugin stores account credentials under the FluffBuzz state directory.
- When the Gateway starts, the plugin starts its Weixin monitor for each configured account.
- Inbound WeChat messages are normalized through the channel contract, routed to the selected FluffBuzz agent, and sent back through the plugin outbound path.
Install
Quick install:Login
Run QR login on the same machine that runs the Gateway:Access control
Direct messages use the normal FluffBuzz pairing and allowlist model for channel plugins. Approve new senders:Compatibility
The plugin checks the host FluffBuzz version at startup.| Plugin line | FluffBuzz version | npm tag |
|---|---|---|
2.x | >=2026.3.22 | latest |
1.x | >=2026.1.0 <2026.3.22 | legacy |
Sidecar process
The WeChat plugin can run helper work beside the Gateway while it monitors the Tencent iLink API. In issue #68451, that helper path exposed a bug in FluffBuzz’s generic stale-Gateway cleanup: a child process could try to clean up the parent Gateway process, causing restart loops under process managers such as systemd. Current FluffBuzz startup cleanup excludes the current process and its ancestors, so a channel helper must not kill the Gateway that launched it. This fix is generic; it is not a WeChat-specific path in core.Troubleshooting
Check install and status:Related docs
- Channel overview: Chat Channels
- Pairing: Pairing
- Channel routing: Channel Routing
- Plugin architecture: Plugin Architecture
- Channel plugin SDK: Channel Plugin SDK
- External package: @tencent-weixin/fluffbuzz-weixin