docs: explain Buzz archived room handling

This commit is contained in:
Shakker
2026-07-31 11:51:36 +01:00
parent bfa0b7e607
commit b3c4ea0291
2 changed files with 8 additions and 1 deletions
+5
View File
@@ -212,6 +212,11 @@ profile subscription does not reach EOSE within 10 seconds, OpenClaw treats the
Buzz relay session as stalled and recycles only that Buzz account connection;
the Gateway keeps running.
Archived rooms are omitted from directory results and live room subscriptions.
If a configured room is archived or restored while OpenClaw is connected, the
plugin recycles only its Buzz connection so the subscription set matches the
relay's current metadata. The Gateway keeps running.
Each configured room uses one room-scoped relay subscription. OpenClaw reserves
three of Buzz's 1,024 connection subscriptions for membership and metadata
queries, so one account can configure up to 1,021 rooms. Near that limit,
+3 -1
View File
@@ -49,7 +49,9 @@ 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.
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: