e8d546c8da
* fix(buzz): page reconnect history instead of dropping older messages On reconnect the Buzz gateway asked the relay for a single capped page of room history and treated EOSE as a complete recovery. Any backlog larger than the per-room replay limit was never requested again, so those messages never reached handleBuzzInbound, the agent, or the session transcript, and nothing reported the loss. The room subscription now records how much history its first page returned and, when that page filled the limit, pages older history through the relay until it is exhausted. Each page is dispatched through the existing bounded replay queue and the next page waits for queue capacity, so recovery stays memory bounded. A room whose backlog cannot be paged past a single timestamp is now reported instead of dropped silently. Membership tracking moves to room-membership-tracker.ts because buzz-bus.ts was already at the 700 line ceiling. * fix(buzz): hold dispatch capacity while a history page is in flight Catch-up asked the replay queue whether capacity existed and then issued the relay query, but nothing held those slots. Live room events arriving while the query was in flight could consume them, so admitting the page afterwards could report overflow, which closes the dispatch queue and drops every queued message before forcing a reconnect. A busy room with slow inbound handlers could repeat that instead of finishing recovery. Capacity is now reserved rather than sampled. reserveCapacity resolves with a reservation that owns its slots until released, page events are admitted through that reservation, and the reservation is released once the page is enqueued. Live enqueues keep the full pending limit and are never rejected earlier because a reservation is outstanding. An overflow reported through a reservation means the relay exceeded the page it was asked for, so it is reported as a history error instead of tearing down the session. * fix(buzz): bound reconnect history pages * fix(buzz): preserve replay reservations * test(buzz): cover catch-up settlement paths * fix(buzz): drain saturated history ranges --------- Co-authored-by: Vincent Koc <vincentkoc@ieee.org>
@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