openclaw/extensions/buzz
Peter Steinberger 4d06fa489b
refactor(channels): deslop smaller channel plugins (#157825)
* refactor(channels): deslop smaller channel plugins

Consolidate duplicated transport, settings, rendering, and lifecycle code across ten bundled plugins. Preserve channel authorization, credential precedence, formatting, CUA tool contracts, path safety, and persisted-state semantics.

Fix double-bracketed Tlon IPv6 ship origins and release downloaded SMS media when sender access is revoked before dispatch. Regression tests fail on the original owners and pass after repair. Related: #157788.

* test(channels): remove retired Buzz runtime barrel inventory
2026-09-24 22:52:40 -07:00
..
assets improve(plugins): give bundled logos consistent white icon tiles (#155259) 2026-09-23 19:09:26 -07:00
src refactor(channels): deslop smaller channel plugins (#157825) 2026-09-24 22:52:40 -07:00
api.ts
channel-plugin-api.ts
directory-contract-api.ts feat: expose Buzz sender and room directory 2026-07-31 13:40:32 +01:00
index.ts
openclaw.plugin.json feat(plugins): define package-owned categories (#142710) 2026-09-09 19:05:40 -07:00
package.json chore(release): close out 2026.9.6 on main (#156869) 2026-09-23 23:02:54 -07:00
qa-runner-api.ts fix(qa): isolate runner discovery facades (#117203) 2026-08-01 13:40:11 +08:00
README.md docs: explain Buzz archived room handling 2026-07-31 13:40:34 +01:00
secret-contract-api.ts
setup-entry.ts
setup-plugin-api.ts
tsconfig.json refactor(plugins): inherit shared package boundary settings (#117474) 2026-08-01 09:11:09 -07:00

@openclaw/buzz

Official Buzz channel plugin for OpenClaw. It connects an OpenClaw agent to approved Buzz rooms for text conversations and threaded replies.

Requirements

You need:

  • A Buzz relay URL
  • A Buzz owner or admin
  • A room where the bot can receive the Bot role

Use wss:// outside local development.

Set up

openclaw channels add --channel buzz

OpenClaw installs the plugin if needed, asks for the relay URL, and generates a dedicated bot identity.

Give the displayed public key only to a Buzz owner or admin:

buzz channels add-member \
  --channel <ROOM_UUID> \
  --pubkey <BOT_PUBLIC_KEY> \
  --role bot

Closed relays may also require the bot to be added as a relay member. Setup waits for approval, discovers accessible rooms, and saves the selected rooms and default target.

Restart the Gateway if it was already running.

Verify

openclaw channels status --probe

Inspect the current bot, approved rooms, and room members:

openclaw directory self --channel buzz
openclaw directory peers list --channel buzz
openclaw directory groups list --channel buzz
openclaw directory groups members --channel buzz --group-id buzz:<ROOM_UUID>

Buzz profile and room names are used as display labels, while public keys and room UUIDs remain the stable identities. Archived rooms are omitted; an archive or restore event rebuilds only the Buzz connection's room subscriptions and does not stop the Gateway.

Send a test message:

openclaw message send \
  --channel buzz \
  --target <ROOM_UUID> \
  --message "Hello from OpenClaw"

Security and scope

  • Never give OpenClaw a human owner's private key.
  • The generated bot private key is stored in OpenClaw configuration; only its public key is displayed.
  • Treat Buzz messages as untrusted agent input.
  • Currently supported: text conversations, threads, typing, and directory lookup in group rooms.
  • Not yet supported: DMs, media, reactions, or creating rooms from OpenClaw.

Full documentation: https://docs.openclaw.ai/channels/buzz

Package: @openclaw/buzz · Plugin ID: buzz